When we use custom or built-in analyzer in our mapping it just convert the stream of characters to stream of tokens.
For example when we analyze the text like The QUICK brown foxes jumped over the dog!.Here i am using custom analyzer which using standard tokenizer and in token filter - lowercase, stemmer Output in lucene index/Inverted index [the,quick,brown,fox,jump,over,the,lazy,dog].
Original text is converted now.The old text is vanished now ? We can't search QUICK beacuse now it is quick , similarly foxes become fox we can't search foxes. Am i saying right?
POST test_index/_doc/1
{
"text_field":"The QUICK brown foxes jumped over the dog!"
}
I am able to search QUICK it should not because we have quick. Does it mean custom analysis is also applied to query string ,I mean when I search for QUICK Elasticsearch analyzer convert this into quick. Because it happens only in search time analysis. And if we are not using search time analysis in our mapping does it means it applying to our mapping automatically.
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.