I would like to know about how we can use own custom analyzer as a
default analyzer instead of standard analyzer.
For examples:
Currently, If any new fields enter into an index will be analyzed using
standard analyzer but, I would like to change this default behaviour by
using own custom analyzer as default analyzer.
I would like to know about how we can use own custom analyzer as a
default analyzer instead of standard analyzer.
For examples:
Currently, If any new fields enter into an index will be analyzed using
standard analyzer but, I would like to change this default behaviour by
using own custom analyzer as default analyzer.
It would be under the index.analysis.analyzer section in your mapping.
Cheers,
Ivan
On Fri, Aug 30, 2013 at 8:17 AM, Ankit Jain <ankitj...@gmail.com<javascript:>
wrote:
Hi All,
I would like to know about how we can use own custom analyzer as a
default analyzer instead of standard analyzer.
For examples:
Currently, If any new fields enter into an index will be analyzed using
standard analyzer but, I would like to change this default behaviour by
using own custom analyzer as default analyzer.
Please help.
Regards,
Ankit Jain
--
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.
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.