We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As of ElasticSearchs documentation (http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#_reserved_characters) the characters '<' and '>' needs to be escaped. However, Lucene does not require this. I've checked out the Util class code and its not escaping those characters.
Yesterday, I had an issue on production server due to a '<' symbol in a query that was not escaped. How are we dealing with this scenario?
I've created my own escape function that adds these two symbols for now. I've also created a PR.
The text was updated successfully, but these errors were encountered:
ab75e5b
Merge pull request #795 from topikito/escape-new-symbols
36165fb
[RFR] Escape new symbols in Util::escapeTerm (fixes #794)
No branches or pull requests
As of ElasticSearchs documentation (http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#_reserved_characters) the characters '<' and '>' needs to be escaped. However, Lucene does not require this. I've checked out the Util class code and its not escaping those characters.
Yesterday, I had an issue on production server due to a '<' symbol in a query that was not escaped. How are we dealing with this scenario?
I've created my own escape function that adds these two symbols for now. I've also created a PR.
The text was updated successfully, but these errors were encountered: