: Thanks for the reply. I was in a hurry and made the URL up to illustrate my
: point. The real query string is more like what you suggest. In any case I'm
: certain that the actual query being used is valid (Solr would complain if it
: weren't) and that the ampersand is somehow affecting results. Is there any

no, actually it wouldn't complain in that case ... a URL param with a name 
it's not expecting would just be ignored.

if you send us the exact URLs you'rehaving problems with there may be 
other nuances about it that we can spot to help figure out your problem. 
(for example: are you absolutely sure the apersand in your field value is 
URL escaped?)

: way I can get Solr to dump some information about how it stores indexes,
: keys, etc. for a certain record? I'm wondering if the ampersand was handled
: in a weird way by my application when the records were added to the index.
: (Although I doubt this since it shows up properly in the facets.) Thanks
: again for your help.

yep, there are a couple of things you can do in general to 
troubleshoot things like this...

1) debugQuery=true ... add that param into your URL and Solr will give you 
some nice debuging info about how your queries are bering parsed.  this is 
important to post when asking followup questions.

2) analysis.jsp ... this is the "Analysis" link on the admin page, it will 
show you how your analyzer is treating the fields you index ... but this 
isn'treally relevant to your specific problem since you are using 
StrField.

3) LukeRequestHandler, in the example schema it's mapped to /admin/luke 
... this will let you see the actual terms indexed for your fields ... but 
this as you said, this isn't going to be much help for you in this 
specific case since you used facet.field to get the value in the first place -- 
that means it's 
definitely indexed that way.

debugQuery=true is definitely your best first step ... send us the exact 
URLs your having problems with (that have debugQuery=true) along with the 
full output of that URL and people can probably help spot your problem.



-Hoss

Reply via email to