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
.
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
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
/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
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
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
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
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
- 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
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:
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:
11 matches
Mail list logo