Hi all,
It seems that there is something about wildcard queries that it is not clear to me
As far as I understand, Wildcard queries are term queries so. the search term is not analysed itself and it is "compared" against the terms in the inverted index.
So suppose that I define an index using the default mappings and I put this document
POST my_test/_doc/1
{
"test_test": "I dream of butterflies instead"
}
and run a wildcard query (I'm just testing the behavior, I know that it is not a good practice to put a * at the front of the search term)
If you are using the default mapping the analyzed field is lowercased, which explains the case insensitivity in your queries. If you queries test_test.keyword you would probably get a different result.
Hi Christian,
Yes I understand that, what I'm not is why my search term is lower cased. It is supposed that the analyzer does not apply to the search term because is a term level query
Thank you
Furthermore, If I create another index with the same field but this time using a custom analyzer (standard tokenizer + stop filter), then the query with
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.