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
Fixed bug where unique results of null values failed to return #2354
Conversation
ivakegg
commented
Apr 19, 2024
- The intermedite results mechanism which got fixed with the most recent unique mechanism resulted in this bug
* The intermedite results mechanism which got fixed with the most recent unique mechanism resulted in this bug
* The query model | ||
*/ | ||
private void setModelMappings(QueryModel model) { | ||
if (model != null) { |
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.
This whole mapping is already done in the DefaultQueryPlanner when setting up the query fields. This was redundant.
if (!values.isEmpty()) { | ||
Collections.sort(values); | ||
String separator = "f-" + field + '/' + (count++) + ":"; |
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.
Adding the count in here is not really useful.
if (keyDocumentEntry.getValue().isIntermediateResult()) { | ||
return keyDocumentEntry; | ||
} | ||
|
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.
This was the critical piece to fix the null document issue.