Fix fields handling in Elasticsearch plugin #54
Merged
Conversation
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
Fix a bug, where the selected fields were removed for a new search. Now we are keeping the fields across multiple searches. For that we are parsing the location and reuse all existing fields. Fix a bug, where the fields list wasn't created, when the search returned less then 10 documents.
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.
Fix a bug, where the selected fields were removed for a new search. Now
we are keeping the fields across multiple searches. For that we are
parsing the location and reuse all existing fields.
Fix a bug, where the fields list wasn't created, when the search
returned less then 10 documents.