Hello,
any ideas on this?
Thank you
Danilo
On 16/11/18 08:48, Danilo Tomasoni wrote:
Thank you for your reply Erick.
I've thought about termsquery but it doesn't support phrase search AFAIK,
and I want to query for near words like "Mycobacterium tuberculosis"
and also i would like to use
Thank you for your reply Erick.
I've thought about termsquery but it doesn't support phrase search AFAIK,
and I want to query for near words like "Mycobacterium tuberculosis" and
also i would like to use
the tilde syntax "Mycobacterium tuberculosis"~2 .
Does it exists a parser for that, so t
You're using edismax which has the "mm" parameter that you can think
of as a sliding scale between pure OR and pure AND. What happens if
you set it to zero?
As for maxboolean clauses, the easiest/fasted way around that would be
to use an "fq" clause and the TermsQueryParser.
Best,
Erick
On Thu, N
On 8/9/2018 7:31 PM, tapan1707 wrote:
I believe correct formats for OR search query are the following:
id:(id1 or id2)
id:id1 or id:id2
The correct form for an OR query is an uppercase "OR". The lowercase
"or" won't do the same thing -- typically it will be interpreted as just
another search
-- From: Rahul R
> Sent: Friday, June 07, 2013 1:21 AM
> To: solr-user@lucene.apache.org
> Subject: Re: OR query with null value and non-null value(s)
>
>
> Thank you Shawn. This does work. To help me understand better, why do
> we need the *:* ? Shouldn't it be impl
Yes, it SHOULD! And in the LucidWorks Search query parser it does. Why
doesn't it in Solr? Ask Yonik to explain that!
-- Jack Krupansky
-Original Message-
From: Rahul R
Sent: Friday, June 07, 2013 1:21 AM
To: solr-user@lucene.apache.org
Subject: Re: OR query with null value an
On 6/6/2013 11:21 PM, Rahul R wrote:
> Thank you Shawn. This does work. To help me understand better, why do
> we need the *:* ? Shouldn't it be implicit ?
> Shouldn't
> fq=(price:4+OR+(-price:[* TO *])) //does not work
> mean the same as
> fq=(price:4+OR+(*:* -price:[* TO *])) //works
>
>
Thank you Shawn. This does work. To help me understand better, why do
we need the *:* ? Shouldn't it be implicit ?
Shouldn't
fq=(price:4+OR+(-price:[* TO *])) //does not work
mean the same as
fq=(price:4+OR+(*:* -price:[* TO *])) //works
Why does Solr need the *:* there ?
On Fri, Jun 7,
On 6/6/2013 12:28 PM, Rahul R wrote:
I have recently enabled facet.missing=true in solrconfig.xml which gives
null facet values also. As I understand it, the syntax to do a faceted
search on a null value is something like this:
&fq=-price:[* TO *]
So when I want to search on a particular value (f
Systems
> Ingram Content Group
> (615) 213-4311
>
>
> -----Original Message-
> From: Michael Jones [mailto:michaelj...@gmail.com]
> Sent: Thursday, January 10, 2013 1:43 PM
> To: solr-user@lucene.apache.org
> Subject: Re: OR query
>
> My fields are
>
> mul
ce Systems
Ingram Content Group
(615) 213-4311
-Original Message-
From: Michael Jones [mailto:michaelj...@gmail.com]
Sent: Thursday, January 10, 2013 1:43 PM
To: solr-user@lucene.apache.org
Subject: Re: OR query
My fields are
And doing
name_long:"paisley, ian"
(constitue
abel:(ian AND paisley)
>>
>> or
>>
>> label:(+ian +paisley)
>>
>> I think this is the case with edismax, which somewhat supports boolean
>> queries but with caveats...
>>
>> You can also turn debugQuery on to figure out why things are not matchin
ure out why things are not matching.
>
> James Dyer
> E-Commerce Systems
> Ingram Content Group
> (615) 213-4311
>
>
> -Original Message-
> From: Michael Jones [mailto:michaelj...@gmail.com]
> Sent: Thursday, January 10, 2013 11:48 AM
> To: solr-user@lucene.apa
riginal Message-
From: Michael Jones [mailto:michaelj...@gmail.com]
Sent: Thursday, January 10, 2013 11:48 AM
To: solr-user@lucene.apache.org
Subject: Re: OR query
I've tried both ways and I still get zero results with this.
Even though name_long:"paisley, ian" will return res
Sent: Thursday, January 10, 2013 7:38 AM
> To: solr-user@lucene.apache.org
> Subject: Re: OR query
>
>
> Thanks, I've tried doing
>
>
> xml
>
> (constituencies:(ian paisley) OR label:(ian paisley) OR office:(ian
> paisley))
>
> name_long:"paisley, ia
-user@lucene.apache.org
Subject: Re: OR query
Thanks, I've tried doing
xml
(constituencies:(ian paisley) OR label:(ian paisley) OR office:(ian
paisley))
name_long:"paisley, ian"
and
+ian +paisley "paisley, ian"
name_long:"paisley, ian"
But neither return any
Thanks, I've tried doing
xml
(constituencies:(ian paisley) OR label:(ian paisley) OR office:(ian
paisley))
name_long:"paisley, ian"
and
+ian +paisley "paisley, ian"
name_long:"paisley, ian"
But neither return any results
On Thu, Jan 10, 2013 at 11:53 AM, Jack Krupansky wrote:
> Use fil
Use filter queries to filter or drill down:
http://wiki.apache.org/solr/CommonQueryParameters#fq
Also consider using dismax/edismax queries, which are designed to match on
any of multiple fields.
Also be careful to put a space between each left parenthesis and field name
since there is a kno
On Oct 3, 2012, at 3:16 PM, Michael Della Bitta
wrote:
> Leading off with a negation does weird things. Try
>
> (*:* AND NOT categoryid:387602) OR mfrid:18678
>
> Michael Della Bitta
>
Yep, works fine in this manner. So, the problem indeed is the leading negate,
even with parentheses, it ig
Your query is really the same as
mfrid:18678 -categoryid:3876021
Which means select all documents with that mfrid value and then exclude from
that set all documents that have the specified categoryid.
Maybe what you wanted is
mfrid:18678 OR (*:* -categoryid:3876021)
or
q=(*:* !categoryid:3
Leading off with a negation does weird things. Try
(*:* AND NOT categoryid:387602) OR mfrid:18678
Michael Della Bitta
Appinions
18 East 41st Street, 2nd Floor
New York, NY 10017-6271
www.appinions.com
Where Influence Isn’t a Game
On Wed, Oct 3
21 matches
Mail list logo
