-
Notifications
You must be signed in to change notification settings - Fork 1.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
Set INDICES_MAX_CLAUSE_COUNT dynamically #13568
Set INDICES_MAX_CLAUSE_COUNT dynamically #13568
Conversation
Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
❌ Gradle check result for dd140e2: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
6ccaa23
to
28d5525
Compare
Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
28d5525
to
4ff1d13
Compare
❌ Gradle check result for 28d5525: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
|
Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
b221209
to
e715516
Compare
❌ Gradle check result for b221209: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for e715516: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for e715516: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
--------- Signed-off-by: Harsha Vamsi Kalluri <[email protected]> (cherry picked from commit c5c6024) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
--------- (cherry picked from commit c5c6024) Signed-off-by: Harsha Vamsi Kalluri <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
--------- Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
…pensearch-project#14436) --------- (cherry picked from commit c5c6024) Signed-off-by: Harsha Vamsi Kalluri <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Signed-off-by: kkewwei <[email protected]>
--------- Signed-off-by: Harsha Vamsi Kalluri <[email protected]>
Description
Changes the
INDICES_MAX_CLAUSE_COUNT_SETTING
to be dynamic instead of being static.This PR is virtually identical to #1527, but there was earlier push back around making this an updateable dynamic setting due to the assumption that users would abuse this setting rather than optimize their underlying query. Lucene has since updated the way the clause counts work and this is now enforced at the
indexSearcher
level -- https://issues.apache.org/jira/browse/LUCENE-8811.More info can be found in #12549 around the motivation for this change, but I ended up raising a PR to make a simple dynamic setting.
Related Issues
Resolves #1526 #12549
Check List
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.