Hi Bast,
Good to know you got it to work - thanks for letting us know!
--
Steve
www.lucidworks.com
> On Sep 2, 2016, at 4:30 AM, Bastien Latard | MDPI AG
> wrote:
>
> Thanks Steve for your advice (i.e.: upgrade to Solr 6.2).
> I finally had time to upgrade and can
Thanks Steve for your advice (i.e.: upgrade to Solr 6.2).
I finally had time to upgrade and can now use "=AND" together with
"=a OR b" and this works as expected.
I even defined the following line in the defaults settings in the
requestHandler, to overwrite the default behavior:
AND
Issue
Hi Steve,
I read the thread you sent me (SOLR-8812) and it seems that the 6.1
includes this fix, as you said.
I will upgrade.
Thank you!
Kind regards,
Bast
On 05/08/2016 14:37, Steve Rowe wrote:
Hi Bastien,
Have you tried upgrading to 6.1? SOLR-8812, mentioned earlier in the thread,
was
Hi Bastien,
Have you tried upgrading to 6.1? SOLR-8812, mentioned earlier in the thread,
was released with 6.1, and is directly aimed at fixing the problem you are
having in 6.0 (also a problem in 5.5): when mm is not explicitly provided and
the query contains explicit operators (except for
Thank you Erick.
You're fully right that it can be an expected behavior to get more docs
with more words...why not...
However, when I set the default OP to "AND" in solrconfig.xml, then a
simple query "q=a OR b" doesn't work as expected... as described in the
previous email:
-> a search
Defaulting to "OR" has been the behavior since forever, so changing the
behavior now is just not going to happen. Making it fit a new version of
"correct" will change the behavior for every application out there that has
not specified the default behavior.
There's no a-priori reason to expect
Thank you Shawn, Jan and Georg for your answers.
Yes, it seems that if I simply remove the defaultOperator it works well
for "composed queries" like '(a:x AND b:y) OR c:z'.
But I think that the default Operator should/could be the AND.
Because when I add an extra search word, I expect that
With Solr 6.0 I've had to set mm=100% & q.op=AND for a full AND query (and
mm=1 & q.op=OR for a full OR query).
Jan Høydahl schrieb am Mo., 25. Apr. 2016 um
16:04 Uhr:
> I think a workaround for your specific case could be to set mm=100% &
> q.op=OR (although it used to
I think a workaround for your specific case could be to set mm=100% & q.op=OR
(although it used to work for q.op=AND before)
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 25. apr. 2016 kl. 14.53 skrev Shawn Heisey :
>
> On 4/25/2016 6:39 AM,
On 4/25/2016 6:39 AM, Bastien Latard - MDPI AG wrote:
> Remember:
> If I add the following line to the schema.xml, even if I do a search
> 'title:"test" OR author:"me"', it will returns documents matching
> 'title:"test" AND author:"me"':
>
The settings in the schema for default field and
t;lat...@mdpi.com.INVALID>:
Hi guys,
How can I set the defaultOperator to be AND?
If I add the following line to the schema.xml, even if I do a search
'title:"test" OR author:"me"', it will returns documents matching
'title:"test" AND author:
<lat...@mdpi.com.INVALID>:
Hi guys,
How can I set the defaultOperator to be AND?
If I add the following line to the schema.xml, even if I do a search 'title:"test" OR author:"me"',
it will returns documents matching 'title:"test" AND author:"me"':
; <lat...@mdpi.com.INVALID>:
>
> Hi guys,
>
> How can I set the defaultOperator to be AND?
> If I add the following line to the schema.xml, even if I do a search
> 'title:"test" OR author:"me"', it will returns documents matching
> 'title:"test" AND
Hi guys,
How can I set the defaultOperator to be AND?
If I add the following line to the schema.xml, even if I do a search
'title:"test" OR author:"me"', it will returns documents matching
'title:"test" AND author:"me"':
solr version: 6.0
I know
14 matches
Mail list logo