BY the way, the fq parameter is being used to apply a facet value as a refinement which is why it is not tokenized and is a string.
jayson.minard wrote: > > I am seeing odd behavior where a query such as: > > http://localhost:8983/solr/select/?q=moss&version=2.2&start=0&rows=10&indent=on&fq=docType%3AFancy+Doc > > works until I add q.op=AND > > http://localhost:8983/solr/select/?q=moss&q.op=AND&version=2.2&start=0&rows=10&indent=on&fq=docType%3AFancy+Doc > > which then causes 0 results. There is only one term in the q parameter, > and the fq parameter I would think would be unaffected, and both of its > terms are there anyway although in a String field and not a tokenized way > (so maybe it is inserting an AND between Fancy AND Doc which isn't > matching the untokenized string anymore?) > > Is there a way to apply q.op to q and not fq at the same time; if that is > indeed the problem? > > Cheers! > -- Jayson > -- View this message in context: http://www.nabble.com/Odd-q.op%3DAND-and-fq-interactions-in-Solr-1.3.0-tp20106953p20106971.html Sent from the Solr - User mailing list archive at Nabble.com.
