R: Query parsing issue

[Francesco Valentini]

Thank you very much,

I've tried both the way that you have suggested to me. Then I've choosen to
re-write the parse method by extending  ExtendedDismaxQParser class.

Francesco.

-Messaggio originale-
Da: Tomás Fernández Löbbe [mailto:tomasflo...@gmail.com] 
Inviato: mercoledì 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 clauses by
extending the splitIntoClauses method?

Tomás


On Wed, Mar 6, 2013 at 6:37 AM, Francesco Valentini 
francesco.valent...@altiliagroup.com wrote:

 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 preprocess the raw query string.

 The phrase querying does not fit my needs because I don’t have to 
 match the entire set of terms/tokens.

 How can I achieve this?



 Thank you in advance.





 Francesco

Query parsing issue

[Francesco Valentini]

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 preprocess the raw query string. 

The phrase querying does not fit my needs because I don’t have to match the 
entire set of terms/tokens. 

How can I achieve this?

 

Thank you in advance.

 

 

Francesco 

 

Re: Query parsing issue

[Tomás Fernández Löbbe]

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, Francesco Valentini 
francesco.valent...@altiliagroup.com wrote:

 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 preprocess the raw query string.

 The phrase querying does not fit my needs because I don’t have to match
 the entire set of terms/tokens.

 How can I achieve this?



 Thank you in advance.





 Francesco

query parsing issue + behavior as OR (solr 1.4-dev)

[Sunil Sarje]

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
solrQueryParser defaultOperator=AND/


Is there any new configuration I need to put in place in order to get this 
working ?

Thanks
-Sunil

Re: query parsing issue + behavior as OR (solr 1.4-dev)

[Norberto Meijome]

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_hijacking

thanks,
B

_
{Beto|Norberto|Numard} Meijome

He could be a poster child for retroactive birth control.

I speak for myself, not my employer. Contents may be hot. Slippery when wet. 
Reading disclaimers makes you go blind. Writing them is worse. You have been 
Warned.