Thanks, Shawn.
We made a change to add q.op=AND as a separate param and found a few issues.
For example, we have a query that filters out guest users in our product.
It boils down to:
select?q=myname*&q.op=AND&fq=(-(site_role:"Guest"))
debugQuery shows this is parsed as the following, which does not work:
+(-(+site_role:Guest))
Previously, because we were setting q.op=AND as a local param, i.e.
"q={!q.op=AND}myname*", my understanding is the effective operator for the
fq param was OR. So the fq param parsed as:
-site_role:Guest
I feel like we can fix the issue by just removing the outer parenthesis.
But I haven't been able to figure out why the operator change (OR to AND)
has this effect.
Any insight appreciated!
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
