parameter or so it seems. No need to change mm in solrconfig nor adding
> > mm
> > > as a query parameter.
> > >
> > > Particularly, I would go with either 2) or 3).
> > >
> > > Best,
> > > Edward
> > >
> > > On Th
Pollard
>
> wrote:
> >
> > Also, I've found this bug from previous which highlights the issue
> > with
> ))~2
> >
> > https://issues.apache.org/jira/browse/SOLR-8812
> >
> > mm is set at config, but not explicitly in the query...
> >
&
seems. No need to change mm in solrconfig nor adding
> mm
> > as a query parameter.
> >
> > Particularly, I would go with either 2) or 3).
> >
> > Best,
> > Edward
> >
> > On Thu, Jan 9, 2020 at 7:47 AM Claire Pollard
> > wrote:
&g
e issue with
> ))~2
> >
> > https://issues.apache.org/jira/browse/SOLR-8812
> >
> > mm is set at config, but not explicitly in the query...
> >
> > I can see this is a change to default behaviour, but does it mean I
> should be passing mm in the quer
; -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 th
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
the parsed query:
Old Query start: +((recordID:[18 TO 18]) (recordID:[19 TO 19]) (recordID:[20 TO
20]))~2
New Query start: +((recordID:[18 TO 18]) (recordID:[19 TO 19]) (recordID:[20 TO
20]))
There shouldn't be a problem using mm with edismax right? Or does the problem
lie with the structure
t;
> >
> >
> > all
> >
> > edismax
> >
> > text^0.4 recordID^10.0
> annotations^0.5 collectionTitle^1.
"boostfuncs":[""],
"timing":{
"time":75.0,
"prepare":{
"time":35.0,
"query":{
"time":35.0},
"facet":{
"time":0.0},
"facet_modul
in helping diagnose what's
going wrong 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 shou
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:
is a LongPointField (sorry I said Int in my previous message).
>
> -Original Message-
> From: Saurabh Sharma
> Sent: 06 January 2020 10:35
> To: solr-user@lucene.apache.org
> Subject: Re: Edismax ignoring queries containing booleans
>
> Please share the query whic
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
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 operators such as AND and OR when searching
> using an IntPointField.
>
> I was hoping to
14 matches
Mail list logo
