So I have 2 mappings one where I use the default Word Delimiter Token
Filter and one where I use a custom one but don't really change any of the
defaults. Both behave different behaviour. I'm not sure why this is
happening.
So I have 2 mappings one where I use the default Word Delimiter Token
Filter and one where I use a custom one but don't really change any of the
defaults. Both behave different behaviour. I'm not sure why this is
happening.
So I have 2 mappings one where I use the default Word Delimiter Token
Filter and one where I use a custom one but don't really change any of the
defaults. Both behave different behaviour. I'm not sure why this is
happening.
So I have 2 mappings one where I use the default Word Delimiter Token
Filter and one where I use a custom one but don't really change any of the
defaults. Both behave different behaviour. I'm not sure why this is
happening.
My aim to use a custom Word Delimiter Token Filter is to change
"stem_english_possessive" to false.
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
Met vriendelijke groet,
Martijn van Groningen
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
I forgot to mention that \u0027 is json notation and when you use it in the
_analyze request body it's not getting converted to an apostrophe. You can
use ''' or quotes instead:
curl -XGET 'localhost:9200/test2/_analyze?analyzer=myAnalyzer&pretty=true'
-d 'world-class player wouldn'''t'
curl -XGET 'localhost:9200/test2/_analyze?analyzer=myAnalyzer&pretty=true'
-d "world-class player wouldn't"
On Tuesday, February 5, 2013 7:25:00 AM UTC-5, Igor Motov wrote:
That looks like a bug that was introduced during Lucene 4 migration. We
will fix it.
On Monday, February 4, 2013 6:12:41 AM UTC-5, Varun Thacker wrote:
Hi Martijn,
I'm using a build against master with all the latest commits.
So I have 2 mappings one where I use the default Word Delimiter Token
Filter and one where I use a custom one but don't really change any of the
defaults. Both behave different behaviour. I'm not sure why this is
happening.
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.