-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confusion over codec parameter to ILM force-merge action #57034
Comments
Pinging @elastic/es-core-features (:Core/Features/ILM+SLM) |
I'm going to guess (since it was a community PR), that Can you explain why you think |
Yes, just that I think of the index setting as simply |
docs still need updating https://www.elastic.co/guide/en/elasticsearch/reference/7.7/ilm-forcemerge.html |
Pinging @elastic/es-docs (>docs) |
#62243 updates the docs to use the current |
@dakrone @DaveCTurner I'm going to close this issue as the docs are now fixed. Please re-open if you feel we need to rename the parameter. |
In #49974 we added support for changing to the
best_compression
codec in ILM's force-merge action, but it seems that the parameter in the REST API is actuallyindex_codec
and notcodec
as per the docs:elasticsearch/x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/ilm/ForceMergeAction.java
Line 36 in 95a7eed
This means the docs for 7.7 are wrong (see #55978). I think
index_codec
is an unfortunate choice of name and it would be preferable to change it tocodec
even though it's now a breaking change so we'd have to do the whole deprecation dance to achieve that.The text was updated successfully, but these errors were encountered: