-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Disable downsampling force merge via mapping metadata #135694
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
Disable downsampling force merge via mapping metadata #135694
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left two questions looks good otherwise 👍
...downsample/src/internalClusterTest/java/org/elasticsearch/xpack/downsample/DownsampleIT.java
Show resolved
Hide resolved
...n/downsample/src/main/java/org/elasticsearch/xpack/downsample/TransportDownsampleAction.java
Outdated
Show resolved
Hide resolved
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💔 Backport failed
You can use sqren/backport to manually backport by running |
In this PR we introduce a mapping metadata field that allows us to skip the force-merge request during a downsamping API request.
When an index has the
downsample.forcemerge.enabledin their mapping metadata, they can enable or disable the force merge:By default, force merge is enabled to match the current user experience.