Hi Chris, Well to start from the bottom of your list there, I restrict my testing to one sku while continuously reindexing the sku after every indexer side change, and reload the core every time also. I just search from the admin page using the word in question and the exact match on the sku field (the unique one) like this: <response> <lst name="responseHeader"> <int name="status">0</int> <int name="QTime">6</int> <lst name="params"> <str name="indent">on</str> <str name="start">0</str> <str name="q">SterlingTek's NB-2LH sku:216473417</str> <str name="bbb">aaaaa</str> <str name="rows">10</str> <str name="version">2.2</str> </lst> </lst>
I will have to find out more about query parsers before I can answer the rest, Will reply to that later... and it's Friday after all! :) Thanks -----Original Message----- From: Chris Hostetter [mailto:hossman_luc...@fucit.org] Sent: Friday, July 15, 2011 4:36 PM To: solr-user@lucene.apache.org Subject: Re: Analysis page output vs. actually getting search matches, a discrepency? : Subject: Analysis page output vs. actually getting search matches, : a discrepency? 99% of the time when people ask questions like this, it's because of confusion about how/when QueryParsing comes into play (as opposed to analysis) -- analysis.jsp only shows you part of the equation, it doesn't know what query parser you are using. you mentioned that you aren't getting matches when you expect them, and you provided the analysis.jsp output, but you didn't mention anything about the request you are making, the query parser used etc.... it owuld be good to know the full query URL, along with the debugQuery output showing the final query toString info. if that info doesn't clear up the discrepency, you should also take a look at the explainOther info for the doc that you expect to match that isn't -- if you still aren't sure what's going on, post all of that info to solr-user and folks can probably help you make sense of it. (all that said: in some instances this type of problem is simply that someone changed the schema and didn't reindex everything, so the indexed terms don't really match what you think they do) -Hoss
