SOLR-18304: Optimize collapse performance for String fields (branch_9x backport)#4635
Open
bartoszfidrysiak wants to merge 4 commits into
Open
Conversation
) Affects Solr 9.x and beyond. As of Lucene 9 (technically late 8.x?), looking up a value became somewhat expensive, motivating being clever to avoid resolving the value. (cherry picked from commit 8088be2)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://issues.apache.org/jira/browse/SOLR-18304
Full description is present in the PR to main branch: #4621.
This PR contains cherry pick of 8088be23 commit from main branch and additionally two Solr 9 compatibility fixes:
mainbranch../gradlew check.