Thank you Upayavira and Shawn. Yes - the query works correctly using
the standard select. I have a workaround where I simply specify the
fields I want to search in each part of the query and do not specify a
df. Just an FYI in case someone else runs into this.
-Joe
On 7/23/2015 10:51 AM, S
On 7/23/2015 7:51 AM, Joseph Obernberger wrote:
> Hi Upayavira - the URL was:
>
> http://server1:9100/solr/MYCOL1/clustering?q=Collection:(COLLECT1008+OR+COLLECT2587)+AND+(amazon+AND+soap)&wt=json&indent=true&clustering=true&rows=1&df=FULL_DOCUMENT&debugQuery=true
>
>
> Here is the relevant part
I've seen something like this on another system - where the OR is
consumed as a query term rather than an operator.
Remember that Edismax will use the Lucene query parser (which supports
OR, etc) unless there is an exception, and defer to dismax if there is a
syntax error.
What I'd suggest here i
Hi Upayavira - the URL was:
http://server1:9100/solr/MYCOL1/clustering?q=Collection:(COLLECT1008+OR+COLLECT2587)+AND+(amazon+AND+soap)&wt=json&indent=true&clustering=true&rows=1&df=FULL_DOCUMENT&debugQuery=true
Here is the relevant part of the response - notice that the default
field (FULL_DOCU
I'd be curious to see the parsed query that you get when adding
debugQuery=true to the URL. I bet that the clustering component is
extracting terms from the parsed query, and perhaps each of those
queries is parsed in some way differently?
Upayavira
On Wed, Jul 22, 2015, at 08:29 PM, Joseph Obern
Upon further investigation, it looks like it is either ignoring the
default field, or when the default field is specified the rest of the
query is ignored.
Example:
q=Field1:(term1 OR term2) AND (item1 OR item2)&df=Field2
that does not cluster correctly, but this does:
q=Field1:(term1 OR term2)
