Jack,
Now I have a direct evidence. I ran Solr under Eclipse and caught that
NGramTokenizer was called from the edismax query parser with "*:*" as
input text.
I have filed a bug with jira:
https://issues.apache.org/jira/browse/SOLR-3962
On 10/15/12 11:32 AM, T. Kuro Kurosaka wrote:
On 10/15/12 10:35 AM, Jack Krupansky wrote:
And you're absolutely certain you see "*:*" being passed to your
analyzer in the final release of Solr 4.0???
I don't have a direct evidence. This is the only theory I have that
explains why changing FieldType causes the sub-optimal scores.
If you know of a way to tell if a tokenizer is really invoked, let me
know.
