&debug=query is your friend. There are several issues that often trip people up:
1> The analysis tab pre-supposes that what you put in the boxes gets
all the way to the field in question. Trivial example:
I put (without quotes) "erick erickson" in the "name" field in the
analysis page and see that it gets tokenized correctly. But the query
"name:erick erickson" actually gets parsed at a higher level into
name:erick default_search_field:erickson. See the discussion at:
SOLR-9185
2> what you think is in your indexed field isn't really. Can happen if
you changed your analysis chain but didn't totally re-index. Can
happen because one of the parts of the analysis chain works
differently than you expect (WordDelimiterFilterFactory, for instance,
has a ton of options that can alter the tokens emitted). The
TermsComponent will let you examine the terms actually _in_ the index
that you search on. You stated that the analysis page shows you what
you expect, so this is a sanity check.
3> You're using edismax and setting some parameter, mm=100% is a
favorite and it's having this effect.
So add debug=query and provide a sample document (or just a field) and
the schema definition for the field in question if you're still
stumped.
Best,
Erick
On Tue, Apr 11, 2017 at 8:35 AM, John Blythe <j...@curvolabs.com> wrote:
> hi everyone.
>
> i recently wrote in ('analysis matching, query not') but never heard back
> so wanted to follow up. i'm at my wit's end currently. i have several
> fields that are showing matches in the analysis tab. when i dumb down the
> string sent over to query it still gives me issues in some field cases.
>
> any thoughts on how to debug to figure out wtf is going on here would be
> greatly appreciated. the use case is straightforward and the solution
> should be as well, so i'm at a loss as to how in the world i'm having
> issues w this.
>
> can provide any amount of contextualizing information you need, just let me
> know what could be beneficial.
>
> best,
>
> john
