AND (*:* AND -field_to_exclude:*)
>
> for edismax defType:
> (+(+(+some_field:hourly) +(+DisjunctionMaxQuery((doc_text_value:*\\:*))
> -field_to_exclude:*)))/no_coord
>
>
> for default defType:
>
>
> +(+some_field:hourly) +(+MatchAllDocsQuery(*:*) -field_to_exclude:
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
Yup
Changes in Solr 7.2: local parameters only parsed when defType is either
"lucene" or "func"
cf. https://lucene.apache.org/solr/guide/7_3/solr-upgrade-notes.html#solr-7-2
cf. https://issues.apache.org/jira/browse/SOLR-11501
On 17 Apr 2019, at 10:35, Michae
Hi everybody,
is it correct that local parameters ( q={!edismax qf=MEDIA_ID v=283813390} ) in
solr only work with the lucene query parser defined for the main query? I tried
with dismax/edismax but it did not work. The documentation is not clear on this
point.
Best regards
Michael Aleythe
fq={!edismax}you are welome
On Mon, Jun 1, 2015 at 6:44 PM, wrote:
> Hello,
>
> I need to parse some complicated queries that only works properly with the
> edismax query parser, in q and fq parameters. I am testing with
> defType=edismax, but it seems that this clause only a
Thank you!
David
De: Shawn Heisey
Para: solr-user@lucene.apache.org,
Fecha: 01/06/2015 18:53
Asunto: Re: fq and defType
On 6/1/2015 10:44 AM, david.dav...@correo.aeat.es wrote:
> I need to parse some complicated queries that only works properly with
the
> edismax query pars
On 6/1/2015 10:44 AM, david.dav...@correo.aeat.es wrote:
> I need to parse some complicated queries that only works properly with the
> edismax query parser, in q and fq parameters. I am testing with
> defType=edismax, but it seems that this clause only affects to the q
> paramet
Hello,
I need to parse some complicated queries that only works properly with the
edismax query parser, in q and fq parameters. I am testing with
defType=edismax, but it seems that this clause only affects to the q
parameter. Is there any way to set edismax to the fq parameter?
Thank you very
field?! That sounds like a particularly lame use of
> Solr.
> >
> > Declare the field as a "string" field and then Solr won't break it up
> into tokens (other than special characters like slash.)
> >
> > Or just set the defType="term" parameter. And t
1) the "terM" parser doesn't use the "df" default field param -- it
requires an "f" local param.
2) because the "f" localparam is required, you can't really use "term" in
defType
3) what you can do is something like this...
q={!
like a particularly lame use of
> Solr.
>
> Declare the field as a "string" field and then Solr won't break it up into
> tokens (other than special characters like slash.)
>
> Or just set the defType="term" parameter. And the term query parser req
)
Or just set the defType="term" parameter. And the term query parser requires
the "f" parameter to be set to the field (maybe that was your NPE). You can
set those parameters in the "defaults" section of the request handler.
Or, you can you the real-time g
om]
Sent: Montag, 12. August 2013 17:10
To: Johannes Elsinghorst
Subject: Re: looking for working example defType=term
How are you using the term query parser? The term query parser requires a
field to be specified.
I use it this way:
q=*:*&fq={!term f=category}electronics
The "t
-- Jack Krupansky
-Original Message-
From: Johannes Elsinghorst
Sent: Monday, August 12, 2013 11:01 AM
To: solr-user@lucene.apache.org
Subject: looking for working example defType=term
Hi,
can anyone provide a working example (solrconfig.xml,schema.xml) using the
TermQParserPlugin? I always
Hi,
can anyone provide a working example (solrconfig.xml,schema.xml) using the
TermQParserPlugin? I always get a Nullpointer-Exception on startup:
8920 [searcherExecutor-4-thread-1] ERROR org.apache.solr.core.SolrCore û
java.lang.NullPointerException
at
org.apache.solr.search.TermQParser
: Saturday, August 10,
2013 6:30 PM To: solr-user@lucene.apache.org Subject: defType
What are the possible options for defType?
lucene
dismax
edismax
Others?
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
t; -Original Message- From: William Bell Sent: Saturday, August 10,
>> 2013 6:30 PM To: solr-user@lucene.apache.org Subject: defType
>> What are the possible options for defType?
>>
>> lucene
>> dismax
>> edismax
>>
>> Others?
>>
>> --
>> Bill Bell
>> billnb...@gmail.com
>> cell 720-256-8076
>
>
>
> --
> Bill Bell
> billnb...@gmail.com
> cell 720-256-8076
>
> -Original Message- From: William Bell Sent: Saturday, August 10,
> 2013 6:30 PM To: solr-user@lucene.apache.org Subject: defType
> What are the possible options for defType?
>
> lucene
> dismax
> edismax
>
> Others?
>
> --
> Bill Bell
> billnb...@gmail.
The full list is in my book. What did you need in particular?
(Actually, I forgot to add "maxscore" to my list.)
-- Jack Krupansky
-Original Message-
From: William Bell
Sent: Saturday, August 10, 2013 6:30 PM
To: solr-user@lucene.apache.org
Subject: defType
What are th
What are the possible options for defType?
lucene
dismax
edismax
Others?
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
There's a difference between q={!myparser f=field}value and
q=field:value&defType=myparser in that the latter requires that your parser do
the splitting of "field" at the colon. Does your parser do this? The former
allows for a local param to specify the f(ield) through
: I am not edismax=true as a flag actually does anything (Solr4 beta):
Alexandre: You are 100% correct, this appears to be a bug in the Admin
UI. Thank you for reporting it...
https://issues.apache.org/jira/browse/SOLR-3811
-Hoss
7;=>0,'docs'=>[]
},
'debug'=>{
'rawquerystring'=>'text',
'querystring'=>'text',
'parsedquery'=>'TitleEN:text',
'parsedquery_toString'=>'TitleEN:text',
&
Thanks for your reply. It worked for me. For now, I am using it in query
string only. But planning to move it to solrconfig.
Thanks again!
~Amitesh
--
View this message in context:
http://lucene.472066.n3.nabble.com/Does-defType-overrides-other-settings-for-default-request-handler
t;/ and
> some *mm * settings. Recently, we have started using *defType=edismax * in
> query params. With this change, we have observed significant drop in results
> count. We doubt that SOLR is using default operator="AND" and hence reducing
> the results count. Please confirm if our
Hi,
We have used *dismax* in our SOLR config with /defaultOperator="OR"/ and
some *mm * settings. Recently, we have started using *defType=edismax * in
query params. With this change, we have observed significant drop in results
count. We doubt that SOLR is using default operator="
> Query 1:
> http://localhost:8085/solr/select/?q=abc&version=2.2&start=0&rows=10&indent=on&defType=dismax
> [defType with capital T -- does not fetch results]
>
> Query 2:
> http://localhost:8085/solr/select/?q=abc&version=2.2&start=0&rows=1
A weird behavior with respect to "defType". Any clues will be appreciated.
Query 1:
http://localhost:8085/solr/select/?q=abc&version=2.2&start=0&rows=10&indent=on&defType=dismax
[defType with capital T -- does not fetch results]
Query 2:
http://localhost:8085/
: Huh, I'm still not completely following. I'm sure it makes sense if you
: understand the underlying implemetnation, but I don't understand how 'type'
: and 'defType' don't mean exactly the same thing, just need to be expressed
: differently in differen
Huh, I'm still not completely following. I'm sure it makes sense if you
understand the underlying implemetnation, but I don't understand how
'type' and 'defType' don't mean exactly the same thing, just need to be
expressed differently in different locatio
: I do understand what they do (at least well enough to use them), but I
: find it confusing that it's called "defType" as a main param, but "type"
: in a LocalParam, when to me they both seem to do the same thing -- which
"type" as a localparam in a que
On Tue, Jul 19, 2011 at 11:41 PM, Jonathan Rochkind wrote:
> Is it generally recognized that this terminology is confusing, or is it just
> me?
>
> I do understand what they do (at least well enough to use them), but I find
> it confusing that it's called "defType&qu
Is it generally recognized that this terminology is confusing, or is it just
me?
I do understand what they do (at least well enough to use them), but I find it
confusing that it's called "defType" as a main param, but "type" in a
LocalParam, when to me they both
On Tue, Jul 19, 2011 at 1:25 PM, Naomi Dushay wrote:
> Regardless, I thought that defType=dismax&q=*:* is supposed to be
> equivalent to q={!defType=dismax}*:* and also equivalent to q={!dismax}*:*
Not quite - there is a very subtle distinction.
{!dismax} is short for {!t
qf_dismax and pf_dismax are irrelevant -- I shouldn't have included
that info. They are passed in the url and they work; they do not
affect this problem.
Your reminder of debugQuery was a good one - I use that a lot but
forgot in this case.
Regardless, I thought that de
On Jul 18, 2011, at 19:15 , Naomi Dushay wrote:
> I found a weird behavior with the Solr defType argument, perhaps with
> respect to default queries?
>
> q={!defType=dismax}*:* hits
this is the confusing one. defType is a Solr request parameter, but not
something that works
dismax does not work with a=*:*
defType=dismax&q=*:* no hits
You need to switch this to:
defType=dismax&q.alt=*:* no hits
On Mon, Jul 18, 2011 at 8:44 PM, Erick Erickson wrote:
> What are qf_dismax and pf_dismax? They are meaningless to
> Solr. Try adding &deb
;ll see output like:
+() ()
showing that your query isn't actually going against
any fields
Best
Erick
On Mon, Jul 18, 2011 at 7:15 PM, Naomi Dushay wrote:
> I found a weird behavior with the Solr defType argument, perhaps with
> respect to default queries?
>
> defType=dismax
I found a weird behavior with the Solr defType argument, perhaps with
respect to default queries?
defType=dismax&q=*:* no hits
q={!defType=dismax}*:* hits
defType=dismax hits
Here is the request handler, which I explicitly indicate:
lu
Sorry for the repost but I posted under DismaxRequestHandler when I should
have listed it as DismaxQueryParser.. ie im using defType=dismax
I have a title field and a description filed. I am searching across both
fields but I don't want description matches unless they are within some sl
42 matches
Mail list logo
