quot;) 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:
(+(+(+some_fi
ontain 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 defType - I
> ge
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 defT
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
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
parameter. Is there any
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
Thank you!
David
De: Shawn Heisey apa...@elyograg.org
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
fq={!edismax}you are welome
On Mon, Jun 1, 2015 at 6:44 PM, david.dav...@correo.aeat.es 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
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
-- 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
. 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 term query parser would never make
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 get handler, /get, which works fine for simple
retrieval
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 requires
the f parameter to be set to the field (maybe that was your
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={!term f=id v=$qq}qq=your_input_id
..where the q param can
.
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
requires the f parameter to be set to the field (maybe that was your
NPE). You can set those parameters
What are the possible options for defType?
lucene
dismax
edismax
Others?
--
Bill Bell
billnb...@gmail.com
cell 720-256-8076
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 the possible
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
@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
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
as: queryParser
name=myparser class=plugin.PayloadTermQueryPlugin/
Now when I am using it as a q parameter it's working fine e.g.:
http://localhost:8983/solr/select?q={!myparser%20f=tag}hidebugQuery=true
But if I specify it in search handler using defType, it is throwing errors:
http
'}},
'response'={'numFound'=34,'start'=0,'docs'=[]
},
'debug'={
'rawquerystring'='text',
'querystring'='text',
'parsedquery'='TitleEN:text',
'parsedquery_toString'='TitleEN:text',
'explain'={},
'QParser'='LuceneQParser',
'timing'={
When I do defType=edismax, I get
: 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
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
* 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 suspicion is correct or are we
missing some
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=AND and hence
A weird behavior with respect to defType. Any clues will be appreciated.
Query 1:
http://localhost:8085/solr/select/?q=abcversion=2.2start=0rows=10indent=ondefType=dismax
[defType with capital T -- does not fetch results]
Query 2:
http://localhost:8085/solr/select/?q=abcversion=2.2start=0rows
Query 1:
http://localhost:8085/solr/select/?q=abcversion=2.2start=0rows=10indent=ondefType=dismax
[defType with capital T -- does not fetch results]
Query 2:
http://localhost:8085/solr/select/?q=abcversion=2.2start=0rows=10indent=ondeftype=dismax
[defType with small T -- perfect
: 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 location.
...
: prefixing def
On Tue, Jul 19, 2011 at 11:41 PM, Jonathan Rochkind rochk...@jhu.edu 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 as a main param
: 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 query string defines the type of query string
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 location.
Sorry for beating a dead horse
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 as a local
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 defType
On Tue, Jul 19, 2011 at 1:25 PM, Naomi Dushay ndus...@stanford.edu wrote:
Regardless, I thought that defType=dismaxq=*:* 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
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 seem to do the same thing
I found a weird behavior with the Solr defType argument, perhaps with
respect to default queries?
defType=dismaxq=*:* no hits
q={!defType=dismax}*:* hits
defType=dismax hits
Here is the request handler, which I explicitly indicate:
requestHandler name=search class
name=parsedquery+() ()/str
showing that your query isn't actually going against
any fields
Best
Erick
On Mon, Jul 18, 2011 at 7:15 PM, Naomi Dushay ndus...@stanford.edu wrote:
I found a weird behavior with the Solr defType argument, perhaps with
respect to default queries?
defType=dismaxq
dismax does not work with a=*:*
defType=dismaxq=*:* no hits
You need to switch this to:
defType=dismaxq.alt=*:* no hits
On Mon, Jul 18, 2011 at 8:44 PM, Erick Erickson erickerick...@gmail.com wrote:
What are qf_dismax and pf_dismax? They are meaningless to
Solr. Try adding
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 slop
42 matches
Mail list logo
