Hoh, I can see that when there are wildcards then KeywordTokenizerFactory is used instead of StandardTokenizerFactory. I created custom wildcard remover char filter for few specific cases (so I cannot use any of regex replacer filters) but event with that, KeywordTokenizerFactory is used.
I thought charFilter is enough but there is more complicated logic in SolrQueryParserBase#handleBareTokenQuery that chooses KeywordTokenizerFactory before my charFilter is invoked! Is it possible to handle custom wildcard remover, so that StandardTokenizerFactory may be used? -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-queries-and-custom-char-filter-tp4107241p4107275.html Sent from the Solr - User mailing list archive at Nabble.com.
