a mm=1 as a query parameter whenever you search for recordID.
> Issuing the parameter in the query will overwrite the mm parameter
> that was setup in solrconfig for that particular query.
>
> 3) Doing a match all query (q=*:*) and moving the recordID query to a
> filter query:
y now rather than just at config level?
-Original Message-
From: Claire Pollard
Sent: 09 January 2020 10:23
To: solr-user@lucene.apache.org
Subject: RE: Edismax ignoring queries containing booleans
Hey Edward,
Thanks for the tips. 😊
I've cleaned up my solrconfig, removed the duplicat
ading the core and see if the query works.
A few remarks based on a snippet of the solrconfig you posted on a previous
e-mail:
* Your solrconfig.xml defines df two times (the debug shows "df":["text",
"text"]);
* There are a couple codes like
and
It would be
e":{
"time":0.0},
"mlt":{
"time":0.0},
"highlight":{
"time":0.0},
"stats":{
"time":0.0},
"expand":{
"time":0.0},
&qu
ong for me?
Cheers,
Claire.
-Original Message-
From: Saurabh Sharma
Sent: 06 January 2020 11:20
To: solr-user@lucene.apache.org
Subject: Re: Edismax ignoring queries containing booleans
It should work well. I have just tested the same with 8.3.0.
Thanks
Saurabh Sharma
On Mon, Jan 6, 2020, 4:
apache.org
Subject: Re: Edismax ignoring queries containing booleans
Please share the query which you are creating.
On Mon, Jan 6, 2020, 3:52 PM Claire Pollard
wrote:
> In Solr 8.3.0 I've got an edismax query parser in my search handler,
> and it seems to be ignoring Boolean operato
In Solr 8.3.0 I've got an edismax query parser in my search handler, and it
seems to be ignoring Boolean operators such as AND and OR when searching using
an IntPointField.
I was hoping to use a query to this field to return a batch of documents with
non-sequential IDs, so a range would be inap
