Hi,
I am upgrading from Solr 6.5.1 to solr 8.6.1 and have noticed a change in
the Edismax parser behavior which is affecting our search results. If user
operators are present in the search query, the Solr 6 behavior was to take
mm parameters from the user query string which was 0% by default if
Hello Guys,
Does Solr support edismax parser with Block Join Parent Query Parser? If
yes then could you provide me the syntax or point me to some reference
document? And how does it affect the performance?
I am working on a search screen in an eCommerce application's backend. The
requireme
“How come edisMax parses *:* as doc_text_value…”
This is arguably a bug, especially because it works as you’d expect if you
put a space after the paren, i.e. ( *:*…
“Does it work the same if I use this clause in q” yes. I know it’s weird,
but use some_field:[* TO *]
Best,
Erick
> On Sep
Hi Erick,
thanks for the response!
I've checked parsed queries in debug mode and there is following
difference:
original query(this is value of the q parameter in the query)
: (some_field:"hourly") AND (*:* AND -field_to_exclude:*)
for edismax defType:
(+(+(+so
nts that
> contain ceratin field".
> Currently, it looks like this:
> *(*:* AND -field_to_exclude:*)*
>
> Full query is:
> *((some_other_field:"value") AND ((*:* AND -field_to_exclude:*)))*
>
> If I use defType=edismax, nothing is found. If I use default defTyp
Hi everyone,
I'm checking Solr query that contains condition "Exclude all documents that
contain ceratin field".
Currently, it looks like this:
*(*:* AND -field_to_exclude:*)*
Full query is:
*((some_other_field:"value") AND ((*:* AND -field_to_exclude:*)))*
If I use de
; >
> >
> >
> >
> >
> >
> >
> > >
> > dictionary="../hunspell_dictionary/en_US.dic"
> >
> > affix="../hunspell_dictionary/en_US.aff" ignoreCase="true" />
> >
> >
> >
> >
> >
> >
> >
ctionary/en_US.aff" ignoreCase="true" />
>
>
>
>
>
>
>
>
>
> *Managed Synonyms:* "abc implement", "bike", "xyz traders", "xyz
> transport"
>
> ---
"xyz traders", "xyz transport"
---------
*Query*: bike
*parser Type:* edismax
-
*Parsed query (from debug)* : +DisjunctionMaxQueryfield1:"abc
implement" field1:bike field1:"xyz traders" field1:"xyz tra
Hello Solarians,
I know how to boost a query and I see the methods for tf and idf in
streaming scripting. What I don’t know is how to incorporate these things
together at a specific percentage of the ranking function.
How do I write a query to use dismax or edismax to rank using 60% tf-idf
score
On 6/15/2020 8:01 AM, Webster Homer wrote:
Only the minus following the parenthesis is treated as a NOT.
Are parentheses special? They're not mentioned in the eDismax documentation.
Yes, parentheses are special to edismax. They are used just like in
math equations, to group and sep
Hello.
Not sure if it's useful or relevant, I encountered another problem with
parentheses (braces) in eDisMax recently
https://issues.apache.org/jira/browse/SOLR-14557.
On Mon, Jun 15, 2020 at 5:01 PM Webster Homer <
webster.ho...@milliporesigma.com> wrote:
> Markus,
> Thanks,
IONE
> 1,3-DIMETHYL-5-(3-PHENYL-ALLYLIDENE)\-PYRIMIDINE-2,4,6-TRIONE
> 1,3-DIMETHYL-5-\(3-PHENYL-ALLYLIDENE\)-PYRIMIDINE-2,4,6-TRIONE
>
> Only the minus following the parenthesis is treated as a NOT.
> Are parentheses special? They're not mentioned in the eDismax
> documen
E-2,4,6-TRIONE
1,3-DIMETHYL-5-(3-PHENYL-ALLYLIDENE)\-PYRIMIDINE-2,4,6-TRIONE
1,3-DIMETHYL-5-\(3-PHENYL-ALLYLIDENE\)-PYRIMIDINE-2,4,6-TRIONE
Only the minus following the parenthesis is treated as a NOT.
Are parentheses special? They're not mentioned in the eDismax documentation.
-Original Message---
> To: solr-user@lucene.apache.org
> Subject: eDismax query syntax question
>
> Recently we found strange behavior in a query. We use eDismax as the query
> parser.
>
> This is the query term:
> 1,3-DIMETHYL-5-(3-PHENYL-ALLYLIDENE)-PYRIMIDINE-2,4,6-TRIONE
>
> It shou
Recently we found strange behavior in a query. We use eDismax as the query
parser.
This is the query term:
1,3-DIMETHYL-5-(3-PHENYL-ALLYLIDENE)-PYRIMIDINE-2,4,6-TRIONE
It should hit one document in our index. It does not. However, if you use the
Dismax query parser it does match the record
tion_de:deutsch description_de:satz))"
But this way it now seems like the “tie” parameter has no impact anymore. The
fact that I wanted something between a sum and a max query was the original
reason why I intend to use a edismax query. Also since I do have full sentences
as query, I tho
Let’s see the results of adding &debug=query to the query, in particular the
parsed version.
Because what you’re reporting doesn’t really make sense. edismax should be
totally
ignoring the “qf” parameter since you’re specifically qualifying all the
clauses with
a field. Unless you’re
xt parts need to stay separate, I want to boost the importance of
(let's say part1) over the other.
My general approach so far has been to get a German translation of the user's
query by sending it to a translation API. Then I want use an edismax query,
since it seems to fulfill all
her:"{"q":"József
Attila"}" description:"{"q":"József Attila"}" author:"{"q":"József
Attila"}",defType=edismax,qf=title^10 author^7 category^5 publisher^3
description,spellcheck=on,pf=title^30 author^14 cate
>
> On Fri, 10 Jan 2020 at 10:46, Edward Ribeiro
> wrote:
>
> > The fq is not affected by mm parameter because it uses Solr's default
> query
> > parser (LuceneQueryParser) that doesn't support it. But you can change
> the
> > parser used by fq this way
s, so
removing it from the solrconfig isn't possible.
I'll let you know how I get on, might be a little while until I get some
results, but thank you again!
Cheers,
Claire.
-Original Message-
From: Edward Ribeiro
Sent: 10 January 2020 05:16
To: solr-user@lucene.apache.org
Subje
ult query
> parser (LuceneQueryParser) that doesn't support it. But you can change the
> parser used by fq this way: fq={!edismax}recordID:(10 20) or fq={!edismax
> mm=1}recordID:(10 20) , for example (even though that is not the case
> here).
>
> Please, let me know if any of
The fq is not affected by mm parameter because it uses Solr's default query
parser (LuceneQueryParser) that doesn't support it. But you can change the
parser used by fq this way: fq={!edismax}recordID:(10 20) or fq={!edismax
mm=1}recordID:(10 20) , for example (even though that is no
l require to match at least 2, that’s the reason of
the ~2). If there are 6 terms then match 4 (6 - 2), and above 6 terms then
matches 90% of the terms (e.g., if there are 10 clauses then it is required
to match at least 9).
> There shouldn't be a problem using mm with edismax right? Or does
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
"\n1.0 = sum of:\n 1.0 = sum
of:\n1.0 = recordID:[19 TO 19]\n",
"F73CFBC7-2CD2-4aab-B8C1-9D19D427EAFB":"\n1.0 = sum of:\n 1.0 = sum
of:\n1.0 = recordID:[20 TO 20]\n"},
The only visual difference I think is the ~2 which came after the initial part
of
t; "q.alt":"*:*",
> "ps":"100",
> "spellcheck.dictionary":["default",
> "wordbreak"],
> "bf":"",
> "echoParams":"all",
> "fl
"text"],
"q.alt":"*:*",
"ps":"100",
"spellcheck.dictionary":["default",
"wordbreak"],
"bf":"",
"echoParams":"all",
"fl":"*,score",
Hi,
We would like to extend SOLR default (named 'lucene' per:
https://lucene.apache.org/solr/guide/6_6/the-standard-query-parser.html)
or eDisMax query parser with additional functionality of Lucene Span queries in
order to allow via standard parsers to execute position search (Span
.xml select/query handlers look like this:
>
>
>
> all
>
> edismax
>
> text^0.4 recordID^10.0
annotations^0.5 collectionTitl
all
edismax
text^0.4 recordID^10.0 annotations^0.5
collectionTitle^1.9 collectionDescription^0.9 title^2.0 Test_FR^1.0 Test_DE^1.0
Test_AR^1.0 genre^1.0 genre_fr^1.0 f
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.
&g
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 wou
;t get the documents with
default score equal to 1.0
-Original Message-
From: Raboah, Avi [mailto:avi.rab...@verint.com]
Sent: Monday, December 09, 2019 2:09 PM
To: solr-user@lucene.apache.org
Subject: RE: Edismax bq(boost query) with filter range on score
I am using solr 7.6.0 and I try to
I am using solr 7.6.0 and I try to check the incl and incu I get the same
result for true or false
-Original Message-
From: Paras Lehana [mailto:paras.leh...@indiamart.com]
Sent: Monday, December 09, 2019 1:31 PM
To: solr-user@lucene.apache.org
Subject: Re: Edismax bq(boost query) with
field from 1.0
> (default score) to max score after boosting.
>
> When I add the frange for example
> bq=text:"Phrase"^3&defType=edismax&fl=*,score&fq={!frange l=0 u=3
> inclusive=true}query($bq)&q=*:*&rows=2000
>
> I get all the documents with sc
Thanks for your fast response!
Without the frange I get all the documents with the score field from 1.0
(default score) to max score after boosting.
When I add the frange for example
bq=text:"Phrase"^3&defType=edismax&fl=*,score&fq={!frange l=0 u=3
inclusive=true}query($
December 09, 2019 7:08 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Edismax bq(boost query) with filter range on score
>
> Hi Raboah,
>
> What do you mean by filter range? Please post expected result. Do you want
> to put an fq on the score?
>
> On Sun, 8 Dec 201
r 09, 2019 7:08 AM
To: solr-user@lucene.apache.org
Subject: Re: Edismax bq(boost query) with filter range on score
Hi Raboah,
What do you mean by filter range? Please post expected result. Do you want to
put an fq on the score?
On Sun, 8 Dec 2019 at 17:54, Raboah, Avi wrote:
> Hi,
>
&
Hi Raboah,
What do you mean by filter range? Please post expected result. Do you want
to put an fq on the score?
On Sun, 8 Dec 2019 at 17:54, Raboah, Avi wrote:
> Hi,
>
> In order to use solr boost mechanism for specific text I use the bq field
> under deftype=edisMax.
>
>
Hi,
In order to use solr boost mechanism for specific text I use the bq field under
deftype=edisMax.
For example -
q=*:*&deftype=edisMax&bq=text:"phrase"^3&fl=*,score
after I do this query I get the relevant documents boosted with the solr
calculation score.
Now my ques
r
Sent: Thu, Jul 18, 2019 04:42 AM
Subject: Re: Solr edismax parser with multi-word synonyms
This is not a phrase query, rather it’s requiring either pair of words
to appear in the title.
You’ve told it that “frozen dinner” and “microwave foods” are synonyms.
So it’s looking for both the words “m
.
You’d see the same thing with single-word synonyms, albeit a little less
confusingly.
Best,
Erick
> On Jul 18, 2019, at 1:01 AM, kshitij tyagi
> wrote:
>
> Hi sunil,
>
> 1. as you have added "microwave food" in synonym as a multiword synonym to
> "frozen
Hi sunil,
1. as you have added "microwave food" in synonym as a multiword synonym to
"frozen dinner", edismax parsers finds your synonym in the file and is
considering your query as a Phrase query.
This is the reason you are seeing parsed query as +(((+title:m
(query with no synonyms)
Here is my first Solr query:
http://localhost:8983/solr/base/search?q=blue+shirt&qf=title&defType=edismax&debugQuery=on
And this is the parsed query I see in the debug output:
+((title:blue) (title:shirt))
Scenario 2: frozen dinner (query with synonyms)
Now
I didn't see any response so I wanted to check if my observation simply is not
relevant for other people or if I missed to provide any required details.
Thanks!
-Original Message-
Date: 05/09/2019 08:28 AM
Subject: Negative boost query (bq) with edismax for lower scores with Solr
Seems like there is a bug with q.op=AND and edismax.
If I understand this correctly, these queries should return the same result:
1) q="a AND b"
2) q="a b" q.op=AND
This is not the case with edismax (using solr 8, LUCENE_VERSION: 8_0_0 ->
had the same problem at least since
I find that the edismax boost query implementation is not quite logical. It
does not allow selectively decreasing the relevancy score anymore.
E.g. bq=color:red^2 can be added to increase the score of matching documents.
But how can I decrease the score for documents with color:red? Before Solr
Hi guys,
I’m just following up from an earlier question I raised on the forum regarding
inconsistencies in edismax query behaviour and I think I may have discovered
the cause of the problem. From testing I've noticed that edismax query
behaviour seems to change depending on the field
e:
Hi,
We are trying to remove stopwords from analysis using edismax parser
parameter.The documentation says
*stopwords
A Boolean parameter indicating if the StopFilterFactory configured in the
query analyzer should be respected when parsing the query. If this is set to
..@wunderwood.org
> http://observer.wunderwood.org/ (my blog)
>
>> On Mar 28, 2019, at 2:47 AM, Ashish Bisht wrote:
>>
>> Hi,
>>
>> We are trying to remove stopwords from analysis using edismax parser
>> parameter.The documentation says
>>
>> *stopwords
>>
; We are trying to remove stopwords from analysis using edismax parser
> parameter.The documentation says
>
> *stopwords
> A Boolean parameter indicating if the StopFilterFactory configured in the
> query analyzer should be respected when parsing the query. If this is set to
> fal
Hi,
We are trying to remove stopwords from analysis using edismax parser
parameter.The documentation says
*stopwords
A Boolean parameter indicating if the StopFilterFactory configured in the
query analyzer should be respected when parsing the query. If this is set to
false, then the
Good afternoon solr community. I'm having an issue debugging an edismax query
which appears to behave differently across two separate collections with what I
believe to be the same default query parameters. Each collection contains
different data but are configured using similar default
on* in the below example). So
*sorting* looks not sufficient.
After playing around with distance functions it turns out this one looks
quite sufficient:
?defType=edismax&q=kind:animal&carnivore&qf=description^3&boost=div(1,abs(sub(weight,50)))
this means: "give me all animals hav
q=kind:animal&wantedweight=50&sort=abs(sub(weight,wantedweight)) asc
Jan Høydahl
> 16. feb. 2019 kl. 17:08 skrev Dave :
>
> Sounds like you need to use code and post process your results as it sounds
> too specific to your use case. Just my opinion, unless you want to get into
> spacial querie
Sounds like you need to use code and post process your results as it sounds too
specific to your use case. Just my opinion, unless you want to get into spacial
queries which is a whole different animal and something I don’t think many have
experience with, including myself
> On Feb 16, 2019, a
Well, you haven't defined "distance" so it's hard to say. But what you
_probably_ want is
to sort by function. See:
https://lucene.apache.org/solr/guide/6_6/function-queries.html
Best,
Erick
On Sat, Feb 16, 2019 at 7:19 AM Nicolas Paris wrote:
>
> Hi
>
> Thanks.
> To clarify, I don't want to sor
Hi
Thanks.
To clarify, I don't want to sort by numeric fields, instead, I d'like to
get sort by distance to my query.
On Thu, Feb 14, 2019 at 06:20:19PM -0500, Gus Heck wrote:
> Hi Niclolas,
>
> Solr has no difficulty sorting on numeric fields if they are indexed as a
> numeric type. Just use "
Hi Niclolas,
Solr has no difficulty sorting on numeric fields if they are indexed as a
numeric type. Just use "&sort=weight asc" If you're field is indexed as
text of course it won't sort properly, but then you should fix your schema.
-Gus
On Thu, Feb 14, 2019 at 4:10 PM David Hastings
wrote:
Not clearly understanding your question here. if your query is
q=kind:animal weight:50 you will get no results, as nothing matches
(assuming a q.op of AND)
On Thu, Feb 14, 2019 at 4:06 PM Nicolas Paris
wrote:
> Hi
>
> I have a numeric field (say "weight") and I d'like to be able to get
> resul
Hi
I have a numeric field (say "weight") and I d'like to be able to get
results sorted.
q=kind:animal weight:50
pf=kind^2 weight^3
would return:
name=dog, kind=animal, weight=51
name=tiger, kind=animal,weight=150
name=elephant, kind=animal,weight=2000
In other terms how to deal with numeric fie
Hi
I use 'edismax'.
Our main language uses compound words.
There is an issue here.
For example, assume that 'ab' => 'a' and 'b' are analyzed.
The results are different when searching with 'ab' and 'a b'.
I want to get the
dd an example to the documentation here:
>
> https://lucene.apache.org/solr/guide/7_6/the-extended-dismax-query-parser.html#using-slop
>
> Elizabeth
>
> On Wed, Jan 23, 2019 at 10:30 PM Yasufumi Mizoguchi <
> yasufumi0...@gmail.com>
> wrote:
>
> > Hi,
> >
will match
> "tnf a"
> "tnf aword1 a"
> "tnf aword1 aword2 a"
>
> On Thu, Jan 24, 2019 at 10:45 AM Danilo Tomasoni
> wrote:
>
>> And what does
>>
>> q: f2:"tnf α"~2
>>
>> f.f2.qf: titles study_b
quot;tnf α"~2
>
> f.f2.qf: titles study_brief_title
>
>
> means with edismax?
>
>
> it raises different results from
>
> q: f2:"tnf α"
>
>
> On 24/01/19 14:51, Elizabeth Haubert wrote:
> > To do this you specify the slop on e
And what does
q: f2:"tnf α"~2
f.f2.qf: titles study_brief_title
means with edismax?
it raises different results from
q: f2:"tnf α"
On 24/01/19 14:51, Elizabeth Haubert wrote:
To do this you specify the slop on each field when you specify the
p
10:30 PM Yasufumi Mizoguchi
wrote:
> Hi,
>
> I am struggling to set per-field slop param in eDisMax query parser with
> Solr 6.0 and 7.6.
> What I want to do with eDixMax is similar to following in the default query
> parser.
>
> * Query string : "aaa bbb"
> *
Hi,
I am struggling to set per-field slop param in eDisMax query parser with
Solr 6.0 and 7.6.
What I want to do with eDixMax is similar to following in the default query
parser.
* Query string : "aaa bbb"
* Target fields : fieldA(TextField), fieldB(TextField)
q=fieldA:"aaa b
edThreadPool.runJob(QueuedThreadPool.java:762)
>at
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680)
>at java.lang.Thread.run(Thread.java:748)
>
> 2018-12-28 15:50:58.809 INFO (qtp1769193365-15) [ x:collection1]
> o.a.s.c.
ams=all&rows=10&wt=xml&debugQuery=true}
>> hits=32 status=0 QTime=8
>
> Neither of those requests includes anything that would change from the
> default lucene parser to edismax. The logging *would* include all parameters
> set by the configuration as well as
s=all&rows=10&wt=xml&debugQuery=true}
hits=32 status=0 QTime=8
Neither of those requests includes anything that would change from the
default lucene parser to edismax. The logging *would* include all
parameters set by the configuration as well as those specified on the URL.
You
Well, I was putting that info out there because I am literally hunting down
this issue without any guidance. The real problem for still is that the Edismax
Query Parser behaves abnormally starting with Version 5 until current giving me
empty parsedQuery. Forcing the request through the Lucene
? Especially, the edismax parser
> which does *not* raise any exception but produces an empty parsedQuery?
> Please, if anyone can help. I feel very lost and without guidance, and
> Google search has not provided me with any help at all.
>
> > On Dec 28, 2018, at 9:57 AM, Kay Wrobel w
Is there any way I can debug the parser? Especially, the edismax parser which
does *not* raise any exception but produces an empty parsedQuery? Please, if
anyone can help. I feel very lost and without guidance, and Google search has
not provided me with any help at all.
> On Dec 28, 2018, a
)
at java.lang.Thread.run(Thread.java:748)
2018-12-28 15:50:58.809 INFO (qtp1769193365-15) [ x:collection1]
o.a.s.c.S.Request [collection1] webapp=/solr path=/select
params={q=ac6023*&defType=lucene&qf=tm_field_product^21.0&qf=tm_title_field^8.0&rows=10&wt=xml&
quot; now shows "+()"; an empty query string.
>
> I can duplicate this result on a 7.5.0 example config by sending an
> edismax query with undefined parameters for df and qf. The other
> field-related parameters for edismax are also undefined. The following
> URL parameter
com/XcNhfdUD>
Notice how "parsedQuery" now shows "+()"; an empty query string.
I can duplicate this result on a 7.5.0 example config by sending an
edismax query with undefined parameters for df and qf. The other
field-related parameters for edismax are also unde
Hi everyone.
I have the task of converting our old SOLR 4.10.2 instance to the current SOLR
7.6.0 version. We're using SOLR as our Search API backend for a Drupal 7
Commerce web site. One of the most basic queries is that a customer would enter
a part number or a portion of a part number on our
Well, the other option is to allow leading wildcards, but use
ReversedWildcardFilterFactory. Admittedly that increases the size of
your index, but apparently your users expect leading wildcards so why
not support them?
Best,
Erick
On Fri, Dec 7, 2018 at 6:58 AM Kudrettin Güleryüz wrote:
>
> Hi,
>
Hi,
I am also wondering how to disable leading wildcards in Solr. Can you
please suggest how to disable leading wildcards in Solr? I know in Lucene
it is a flag that's set to false by default.
> Do it on the client side. Just don't allow leading asterisks or question
marks in your query term.
Th
Hello,
I'm trying to perform the following query with edismax parser and
sub-queries of edismax type.
f.f3.qf=...
f.f4.qf=...
f.f5.qf=...
((_query_:{!edismax qf="abstracts abstract_background abstract_objective
abstract_methods abstract_results abstract_conclusions abstr
Hello,
Sorry for trying this once more. Is there anyone around who can help me, and
perhaps others, on this subject and the linked Jira ticket and failing test?
I could really need some help from someone who is really familiar with edismax
code and the underlying QueryBuilder parts that are
kus Jelsma
> Sent: Sunday 18th November 2018 23:21
> To: solr-user@lucene.apache.org; solr-user
> Subject: RE: KeywordRepeat, stemming, (single term) synonyms and minimum
> should match (edismax)
>
> Hello,
>
> Apologies for bothering you all again, but i really need
arkus
-Original message-
> From:Markus Jelsma
> Sent: Tuesday 13th November 2018 9:52
> To: solr-user
> Subject: KeywordRepeat, stemming, (single term) synonyms and minimum should
> match (edismax)
>
> Hello, apologies for this long winded e-mail.
>
> O
[1].
We use a custom QParser extending edismax and also extend
ExtendedSolrQueryParser, so we are able to override newFieldQuery in case we
have to. The problem also directly applies to Solr's vanilla edismax. The file
synonyms.txt contains the stemmed versions of the original terms.
Con
Followup:
I had a theory that Nicky tested, and I think what was observed confirms the
theory.
TL;DR:
In previous versions, I think there was a bug where the presence of boolean
operators caused edismax to ignore the mm parameter, and only rely on the
boolean operator(s).
After that bug got
Hi,
What is your full query path or URL that you pass for the query?
And how is your setting like for the edismax in your solrconfig.xml?
Regards,
Edwin
On Fri, 26 Oct 2018 at 06:24, Nicky Mastin wrote:
>
> Oddity with edismax and queries involving boolean operators. Here
Oddity with edismax and queries involving boolean operators. Here's the
"parsedquery_toString" from two different queries:
input: "dog AND kiwi":
https://apaste.info/gaQl
input: "dog OR kiwi":
https://apaste.info/sBwa
Both queries return the same number o
ch wrote:
> Hi,
>
> I'm having issues getting an edismax query to match a certain document via
> a particular field ("name_c"). I believe this issue is related to
> whitespace removal and field/edismax configuration.
>
> *Search term:* "viet nam"
&g
Hi,
I'm having issues getting an edismax query to match a certain document via
a particular field ("name_c"). I believe this issue is related to
whitespace removal and field/edismax configuration.
*Search term:* "viet nam"
*Document name
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 do
On 9/10/2018 5:45 PM, dshih wrote:
Based on what you said, is my query supposed to work as is if I set
luceneMatchVersion=7.1.0? It does not appear to.
It does look like a luceneMatchVersion check was added to the change in
SOLR-11501, so I would expect that to work. Setting luceneMatchVersi
Thanks Shawn!
Based on what you said, is my query supposed to work as is if I set
luceneMatchVersion=7.1.0? It does not appear to.
Also, my understanding is using the local param makes the AND apply only to
the following search terms provided to the "q" query string. If I add a
q.op=AND as a se
On 9/7/2018 6:59 PM, dshih wrote:
Query:
/select?q={!q.op=AND}mysearchtext*&defType=edismax&debugQuery=true
Result:
"querystring": "{!q.op=AND}mysearchtext*",
"parsedquery": "+DisjunctionMaxQuery(((Synonym(text:q
text:qopandmysearchtext text
SOLR 7.4.0
Apologies if this has been answered, but I can't find the answer for the
life of me if it has been.
Query:
/select?q={!q.op=AND}mysearchtext*&defType=edismax&debugQuery=true
Result:
"querystring": "{!q.op=AND}mysearchtext*",
"parsedquery&qu
having an issue where if i use edismax and search:
(creator:(Michael Carrier))
it goes to the default operator of AND so gets results where creator has
both those words in it.
however when a boolean is present:
*((pharmacy)) AND (creator:(Michael Carrier))*
*it seems to revert to OR and do a
1 - 100 of 940 matches
Mail list logo
