Add missing support for escape to QueryStringQueryBuilder #13016
Conversation
This file contains 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
|
LGTM |
QueryStringQueryParser parses `escape`, but java api users had no chance to actually set it. Closes elastic#13016
javanna
force-pushed
the
fix/query_string_escape
branch
from
7e05c69
to
9e67c65
Compare
javanna
added a commit
that referenced
this pull request
Aug 21, 2015
QueryStringQueryParser parses `escape`, but java api users had no chance to actually set it. Closes #13016
clintongormley
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
QueryStringQueryParser parses
escape, but java api users had no chance to actually set it.