By default, string fields are analyzed in elasticasearch. It means that
"order-staging-541" is indexed as 3 terms "order", "staging" and "541". You
query is also analyzed, and it's also converted into 3 terms "order",
"staging" and "541" no matter which special characters are in between.
That's why they are matching. If you want to search this field exactly as
it is, you should reindex it as "index":"not_analyzed".
On Monday, April 9, 2012 4:40:23 PM UTC-4, JP Toto wrote:
Hi all!
Sorry if this has been covered. I tried to do my searching first.
It throws a syntax error. I am trying to follow the Lucene special
characters escaping protocol laid out here Apache Lucene - Query Parser Syntax at
the bottom but I'm still receiving syntax errors.
Thanks, Igor! I came to that realization today. Got it fixed. I appreciate
the feedback
On Tue, Apr 10, 2012 at 4:28 PM, Igor Motov imotov@gmail.com wrote:
By default, string fields are analyzed in elasticasearch. It means that
"order-staging-541" is indexed as 3 terms "order", "staging" and "541". You
query is also analyzed, and it's also converted into 3 terms "order",
"staging" and "541" no matter which special characters are in between.
That's why they are matching. If you want to search this field exactly as
it is, you should reindex it as "index":"not_analyzed".
On Monday, April 9, 2012 4:40:23 PM UTC-4, JP Toto wrote:
Hi all!
Sorry if this has been covered. I tried to do my searching first.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.