please create full reproduction of the steps that you did. The above snippet does have any information where you used that analyzer in your mapping, as you need to conifgure it for the field you want to use it for.
Thanks for your suggestion. Performance is very important in our application. We are changing from solr to elastic because of performance. So I don't want to slow down performance. Please let me know if there is any other solution for this.
the suggested approach is to use multiple fields as I suggested in my first answer in that post. Queries will be fast then but of course the additional field will require additional disk space in the index.
I am just converting user input to lower-case. Below is my query:
"filter": { "or": [ { "term": { "User": "test" } },{ "term": { "Message": "test" } } ] }
This query shows exact word result with case-insensitivity.
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.