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

[Backport 2.x] Enable numeric sort optimisation for few numerical sort types #6330

Merged
merged 1 commit into from
Feb 15, 2023

Conversation

opensearch-trigger-bot[bot]
Copy link
Contributor

Backport 6bb9e3e from #6321.

This commit restores the sort optimization to use BKD to skip non-competitive
docs for numeric types whose BYTES size match between the BKD leaf and doc
values encoding. For now this is only LONG, DOUBLE, DATE, and DATE_NANOSECONDS
as the remaining NumericTypes use 64bit docvalue encoding while the BKD uses
smaller byte encoded space.

This also updates the QueryPhase to remove the long time unnecessary in order
doc id check and minDoc boolean query for skipping non-competitive docs that is
handled by all Lucene 7.0+ sorted indexes.

Existing tests are updated.

Signed-off-by: Nicholas Walter Knize <nknize@apache.org>
Signed-off-by: gashutos <gashutos@amazon.com>

Co-authored-by: Nicholas Walter Knize <nknize@apache.org>
Co-authored-by: Chaitanya Gohel <gashutos@amazon.com>
(cherry picked from commit 6bb9e3e)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@github-actions
Copy link
Contributor

Gradle Check (Jenkins) Run Completed with:

@nknize nknize merged commit 4aeae87 into 2.x Feb 15, 2023
@github-actions github-actions bot deleted the backport/backport-6321-to-2.x branch February 15, 2023 18:32
@nknize nknize added Performance This is for any performance related enhancements or bugs v2.6.0 'Issues and PRs related to version v2.6.0' labels Feb 15, 2023
@nknize
Copy link
Collaborator

nknize commented Feb 15, 2023

Do we want to backport this as a bugfix for all 2.x releases?

@andrross
Copy link
Member

andrross commented Feb 15, 2023

Do we want to backport this as a bugfix for all 2.x releases?

I vote no because 2.6 is only a couple weeks out now so a 2.5.1 patch release seems unlikely, and we'd want to keep such a patch release lean anyway to address critical issues without introducing new problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Performance This is for any performance related enhancements or bugs v2.6.0 'Issues and PRs related to version v2.6.0'
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants