Re: ComplexPhraseQueryParser with multiple fields

2011-06-23 Thread lichman
Which patch are you referring to? The last one? And sure... I'll do the voting thing. -- View this message in context: http://lucene.472066.n3.nabble.com/ComplexPhraseQueryParser-with-multiple-fields-tp2879290p3099032.html Sent from the Lucene - Java Users mailing list archive at Nabble.com

Re: ComplexPhraseQueryParser with multiple fields

2011-06-23 Thread lichman
. Any ideas? -- View this message in context: http://lucene.472066.n3.nabble.com/ComplexPhraseQueryParser-with-multiple-fields-tp2879290p3099397.html Sent from the Lucene - Java Users mailing list archive at Nabble.com

Re: ComplexPhraseQueryParser with multiple fields

2011-06-23 Thread Ahmet Arslan
By the way - I'm using the ComplexPhraseQueryParser that I've downloaded from: https://issues.apache.org/jira/browse/SOLR-1604 And I've tried to use packages: - org.apache.lucene.search - org.apache.lucene.queryParser Both, when compiled and added to the SOLR lib dir, caused the

Re: ComplexPhraseQueryParser with multiple fields

2011-06-23 Thread lichman
/ComplexPhraseQueryParser-with-multiple-fields-tp2879290p3099495.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h

Re: ComplexPhraseQueryParser with multiple fields

2011-06-23 Thread Ahmet Arslan
But now there's another issue. I'm using SOLR and Lucene 3.1.0 and when sending a query Wildcard* phrase* it works as expected - but, when sending the query wildcard* (Only one word withing the phrase) I'm getting another exception: HTTP ERROR: 500 Unknown query type

Re: ComplexPhraseQueryParser with multiple fields

2011-06-23 Thread lichman
The same as touch*. Thanks. -- View this message in context: http://lucene.472066.n3.nabble.com/ComplexPhraseQueryParser-with-multiple-fields-tp2879290p3099824.html Sent from the Lucene - Java Users mailing list archive at Nabble.com

Re: ComplexPhraseQueryParser with multiple fields

2011-06-22 Thread Ahmet Arslan
Which of the solutions did you find to work better? Can you please say which package should I change it to if I choose to do it that way? I think changing package name of ComplexQueryParser is easier. This way you can use existing patch directly. Plus, do you mind voting

Re: ComplexPhraseQueryParser with multiple fields

2011-06-21 Thread lichman
Say, Which of the solutions did you find to work better? Can you please say which package should I change it to if I choose to do it that way? Thanks, Moshe Lichman. -- View this message in context: http://lucene.472066.n3.nabble.com/ComplexPhraseQueryParser-with-multiple-fields

Re: ComplexPhraseQueryParser with multiple fields

2011-05-03 Thread Chris Salem
- Original Message - To: java-user@lucene.apache.org java-user@lucene.apache.org, Chris Salem ch...@mainsequence.net From: Ahmet Arslan iori...@yahoo.com Sent: 5/2/2011 6:42:37 AM Subject: Re: ComplexPhraseQueryParser with multiple fields Hi, I've just started using the ComplexPhraseQueryParser

Re: ComplexPhraseQueryParser with multiple fields

2011-05-02 Thread Ahmet Arslan
Hi, I've just started using the ComplexPhraseQueryParser and it works great with one field but is there a way for it to work with multiple fields?  For example, right now the query: job_title: sales man* AND NOT contact_name: Chris Salem throws this exception Caused by:

ComplexPhraseQueryParser with multiple fields

2011-04-29 Thread Chris Salem
Hi, I've just started using the ComplexPhraseQueryParser and it works great with one field but is there a way for it to work with multiple fields? For example, right now the query: job_title: sales man* AND NOT contact_name: Chris Salem throws this exception Caused by: