Try using multi field on the original field:
One field and use an analyzer with a path hierarchy tokenizer and another
field can be non-analyzed. The term filter should be used on non-analyzed
fields (or with analyzers that only produce one token (lowercase,
ascii-folding, etc..).
--
Ivan
On Fri, Jun 14, 2013 at 3:49 AM, Erik Fäßler khituras@gmail.com wrote:
I'm not sure I exactly understood the question.
What does not work as desired? You can do term queries (
Elasticsearch Platform — Find real-time answers at scale | Elastic) which
should be "exact-match", if this is what you mean?On Friday, 14 June 2013 08:05:09 UTC+2, Allan Johns wrote:
Is this possible?
I have an analyzer using a path hierarchy tokenizer that I use on a
particular field. This works fine, but sometimes I want to do an
exact-match on the field. I can't quite work out how to get this working
though.Thanks
A--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.