Hmmm, there are two things you _must_ get familiar with when diagnosing
these ..
1> admin/analysis. That'll show you exactly what the analysis chain does,
and it's
not always obvious.
2> add &debug=query to your input and look at the parsed query results. For
instance,
this "name:4nSolut
solr-user-unsubscribe
2013/5/28 Michał Matulka
> Thanks for your responses, I must admit that after hours of trying I
> made some mistakes.
> So the most problematic phrase will now be:
> "4nSolution Inc." which cannot be found using query:
>
> name:4nSolution
>
> or even
>
> name:4nSolution
Thanks for your responses, I must admit
that after hours of trying I made some mistakes.
So the most problematic phrase will now be:
"4nSolution Inc." which cannot be found using query:
name:4nSolution
or even
name:4nSolution Inc.
Hmmm, with 4.x I get much different behavior than you're
describing, what version of Solr are you using?
Besides Alex's comments, try adding &debug=query to the url and see what comes
out from the query parser.
A quick glance at the code shows that DefaultAnalyzer is used, which doesn't do
any an
What does analyzer screen say in the Web AdminUI when you try to do that?
Also, what are the tokens stored in the field (also in Web AdminUI).
I think it is very strange to have TextField without a tokenizer chain.
Maybe you get a standard one assigned by default, but I don't know what the
standa
