dì 6 marzo 2013 19:39
A: solr-user@lucene.apache.org
Oggetto: Re: Query parsing issue
It should be easy to extend ExtendedDismaxQParser and do your pre-processing
in the parse() method before calling edismax's parse. Or maybe you could
change the way EDismax is splitting the input query into claus
It should be easy to extend ExtendedDismaxQParser and do your
pre-processing in the parse() method before calling edismax's parse. Or
maybe you could change the way EDismax is splitting the input query into
clauses by extending the "splitIntoClauses" method?
Tomás
On Wed, Mar 6, 2013 at 6:37 AM,
Hi,
I’ve written my own analyzer to index and query a set of documents. At indexing
time everything goes well but
now I have a problem in query phase.
I need to pass the whole query string to my analyzer before the edismax query
parser begins its tasks.
In other words I have to prepro
On Mon, 20 Oct 2008 06:21:06 -0700 (PDT)
Sunil Sarje <[EMAIL PROTECTED]> wrote:
> I am working with nightly build of Oct 17, 2008 and found the issue that
> something wrong with LuceneQParserPlugin; It takes + as OR
Sunil, please do not hijack the thread :
http://en.wikipedia.org/wiki/Thread_hi
I am working with nightly build of Oct 17, 2008 and found the issue that
something wrong with LuceneQParserPlugin; It takes + as OR
e.g. q=first_name:joe+last_name:smith is behaving as OR instead of AND.
Default operator is set to AND in schema.xml
Is there any new configuration I need to put
