y way to compile
> > an
> > > eDismax query parser on it's own that works with Solr 1.4, and then
> just
> > > drop it into your local lib/ for use with an existing Solr 1.4?
> > >
> > > Jonathan
> > >
> > > __
nd then just
> > drop it into your local lib/ for use with an existing Solr 1.4?
> >
> > Jonathan
> >
> >
> > From: Daniel Pötzinger [daniel.poetzin...@aoemedia.de]
> > Sent: Thursday, January 27, 2011 9:26 AM
> >
our local lib/ for use with an existing Solr 1.4?
>
> Jonathan
>
>
> From: Daniel Pötzinger [daniel.poetzin...@aoemedia.de]
> Sent: Thursday, January 27, 2011 9:26 AM
> To: solr-user@lucene.apache.org
> Subject: AW: DismaxParser Query
>
]
Sent: Thursday, January 27, 2011 9:26 AM
To: solr-user@lucene.apache.org
Subject: AW: DismaxParser Query
It may also be an option to mix the query parsers?
Something like this (not tested):
q={!lucene}field1:test OR field2:test2 _query_:{!dismax qf=fields}+my dismax
-bad
So you
...@gmail.com]
Gesendet: Donnerstag, 27. Januar 2011 15:15
An: solr-user@lucene.apache.org
Betreff: Re: DismaxParser Query
What version of Solr are you using, and could you consider either 3x or
applying a patch to 1.4.1? Because eDismax (extended dismax) handles the
full Lucene query language and
What version of Solr are you using, and could you consider either 3x or
applying a patch to 1.4.1? Because eDismax (extended dismax) handles the
full Lucene query language and probably works here. See the Solr
JIRA 1553 at https://issues.apache.org/jira/browse/SOLR-1553
Best
Erick
On Thu, Jan 27,
with dismax you get to say things like match all terms if less then 3 terms
entered else match term-x
it produces highly flexible and relevant matches and works very well in lots
of common search usescases. field boosting
allows further tuning.
if you have rigid rules like the last one you quote i
It worked by making mm=0 (it acted as OR operator)
but how to handle this
field1:((keyword1 AND keyword2) OR (keyword3 AND keyword4)) OR
field2:((keyword1 AND keyword2) OR (keyword3 AND keyword4)) OR
field3:((keyword1 AND keyword2) OR (keyword3 AND keyword4))
On 27 January 2011 17:06, lee carr
sorry ignore that - we are on dismax here - look at mm param in the docs
you can set this to achieve what you need
On 27 January 2011 11:34, lee carroll wrote:
> the default operation can be set in your config to be "or" or on the query
> something like q.op=OR
>
>
>
> On 27 January 2011 11:26,
The DisMax query parser internally hard-codes its operator to OR.
This is quite unlike the Lucene query parser, for which the default operator
can be configured using the solrQueryParser in schema.xml
Regards,
Bijeet Singh
On Thu, Jan 27, 2011 at 4:56 PM, Isan Fulia wrote:
> but q="keyword1 key
the default operation can be set in your config to be "or" or on the query
something like q.op=OR
On 27 January 2011 11:26, Isan Fulia wrote:
> but q="keyword1 keyword2" does AND operation not OR
>
> On 27 January 2011 16:22, lee carroll
> wrote:
>
> > use dismax q for first three fields an
but q="keyword1 keyword2" does AND operation not OR
On 27 January 2011 16:22, lee carroll wrote:
> use dismax q for first three fields and a filter query for the 4th and 5th
> fields
> so
> q="keyword1 keyword 2"
> qf = field1,feild2,field3
> pf = field1,feild2,field3
> mm=something sensible f
use dismax q for first three fields and a filter query for the 4th and 5th
fields
so
q="keyword1 keyword 2"
qf = field1,feild2,field3
pf = field1,feild2,field3
mm=something sensible for you
defType=dismax
fq=" field4:(keyword3 OR keyword4) AND field5:(keyword5)"
take a look at the dismax docs for
Hi all,
The query for standard request handler is as follows
field1:(keyword1 OR keyword2) OR field2:(keyword1 OR keyword2) OR
field3:(keyword1 OR keyword2) AND field4:(keyword3 OR keyword4) AND
field5:(keyword5)
How the same above query can be written for dismax request handler
--
Thanks & Reg
14 matches
Mail list logo
