add support for zstd compressed corpora

[OVI3D0]

Description

Adds a workload param so users can use the new zstd compressed corpora by passing in:
--workload-params=use_zst:true
Only applies to the larger workloads where ZSTD compressed corpora have been added.

Issues Resolved

#357

Testing

• New functionality includes testing

Tested by running workloads using new param.

Backport to Branches:

• 6
• 7
• 1
• 2
• 3

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[gkamat]

Would zstd be a better suffix, since that seems to be the commonly used abbreviation for Zstandard? If this is changed, the workload parameter should be changed to correspond as well.

[OVI3D0]

I think you're right. The param is now use_zstd in the latest revision

[gkamat]

These names would probably need to change, since the documents-1000-part* are the contributing chunks for the bzip2 corpus.

[OVI3D0]

I uploaded new chunks to the s3 bucket for the ZSTD compressed corpora. They're now called documents-1000-zstd-part*

[gkamat]

Perhaps the document-count and uncompressed-bytes should be moved out of the Jinja if markup? That would eliminate the duplication. Might be a bit more work for http_logs but still probably worth it.

[OVI3D0]

You're right, this looks a lot cleaner. Reduced quite a few lines of code as well

[gkamat]

Nit: "relies on"

[IanHoang]

@OVI3D0 @gkamat When users list out workloads with opensearch-benchmark list workloads, should we include a new column listing out all the compressed extensions each workload supports? This would help users understand quickly which workloads can use zstd

[OVI3D0]

@OVI3D0 @gkamat When users list out workloads with opensearch-benchmark list workloads, should we include a new column listing out all the compressed extensions each workload supports? This would help users understand quickly which workloads can use zstd

I think this would be helpful. I can open up a separate PR for this

[opensearch-trigger-bot]

The backport to 7 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-7 7
# Navigate to the new working tree
pushd ../.worktrees/backport-7
# Create a new branch
git switch --create backport/backport-542-to-7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a593f0ce7099550c2ccaa65ef8d45447877e36e5
# Push it to GitHub
git push --set-upstream origin backport/backport-542-to-7
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-7

Then, create a pull request where the base branch is 7 and the compare/head branch is backport/backport-542-to-7.