On other hand, If I use a single query_string instead of bool of terms it works. Does ES/lucene determines not to use the word-separators by looking at the definition of the fields.
On Friday, September 19, 2014 11:05:59 AM UTC-4, Ankush Jhalani wrote: > > In our search we have configured text with 2 analyzers, english and > standard so we can match phrases on the standard-analyzer. We break the > keywords by space, and create a bool query for each word. > > This is working fine for all cases except where the query has standard > word-separators like & (ampersand), ; (semi-colon), etc. As > word-separators are stripped in index by analyzer, searching for them > returns 0 results. Gist. > https://gist.github.com/ajhalani/3def3ea7caec5cd58490 > > I don't want to use a whitespace analyzer because we do actually want to > ignore word separators. I was thinking about hacky workarounds like > removing all standalone non-alphanumeric characters, or moving them in > "should" instead of default "must" (in case we do have analyzers in future > that are whitespace). > > Thanks in advance. > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4b205133-eecd-490a-a028-9a53a3230973%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
