Skip to content
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

Make sure _forcemerge respects max_num_segments. #32291

Merged
merged 1 commit into from
Jul 26, 2018

Commits on Jul 23, 2018

  1. Make sure _forcemerge respects max_num_segments.

    An upcoming [Lucene change](https://issues.apache.org/jira/browse/LUCENE-7976)
    will make TieredMergePolicy respect the maximum merged segment size all the
    time, meaning it will possibly not respect the `max_num_segments` parameter
    anymore if the shard is larger than the maximum segment size.
    
    This change makes sure that `max_num_segments` is respected for now in order
    to give us time to think about how to integrate this change, and also to delay
    it until 7.0 as this might be a big-enough change for us to wait for a new
    major version.
    jpountz committed Jul 23, 2018
    Configuration menu
    Copy the full SHA
    7b494be View commit details
    Browse the repository at this point in the history