You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose we add documentation that 1) describes each codec, their pros, cons and tradeoffs, provide links to benchmarks, 2) explain what can and cannot be done at runtime (e.g. can one change a codec after the index is created? can one restore a snapshot that used a certain codec into an index that uses another?).
The text was updated successfully, but these errors were encountered:
Naarcha-AWS
added
1 - Backlog
Issue: The issue is unassigned or assigned but not started
Sev3
Medium priority. Content that's missing, driven by dev, PM or the community.
and removed
untriaged
labels
May 1, 2023
What do you want to do?
Tell us about your request. Provide a summary of the request and all versions that are affected.
In opensearch-project/OpenSearch#3354 we've introduced some new experimental compression codecs . The documentation is sparse on what this does, in https://opensearch.org/docs/1.0/opensearch/rest-api/create-index/ we only say that
index.codec
is "The compression type to use to compress stored data. Available values are best_compression and default."I propose we add documentation that 1) describes each codec, their pros, cons and tradeoffs, provide links to benchmarks, 2) explain what can and cannot be done at runtime (e.g. can one change a codec after the index is created? can one restore a snapshot that used a certain codec into an index that uses another?).
The text was updated successfully, but these errors were encountered: