RE: ComplexPhraseQueryParser (Expanded Form and Boosting)

2010-02-02 Thread Haghighi, Nariman
sday, February 02, 2010 9:32 AM To: java-user@lucene.apache.org Subject: Re: ComplexPhraseQueryParser (Expanded Form and Boosting) > Second concern: boosting a > phrase ("java developer"^10.0) doesn't seem to be applied > when you look at the result explanations when using the >

Re: ComplexPhraseQueryParser (Expanded Form and Boosting)

2010-02-02 Thread Ahmet Arslan
> Second concern: boosting a > phrase ("java developer"^10.0) doesn't seem to be applied > when you look at the result explanations when using the > ComplexPhraseQueryParser - it's respected on single word > queries and it's respected on phrases using the basic > QueryParser. I just tested and abl

Re: ComplexPhraseQueryParser (Expanded Form and Boosting)

2010-02-02 Thread Karsten F.
Hi Nariman, In my understanding of ComplexPhraseQueryParser this class is not longer supported. http://issues.apache.org/jira/browse/LUCENE-1486#action_12782254 Instead with lucene 3.1 the new org.apache.lucene.queryParser.standard.parser.StandardSyntaxParser will do this job. https://issues.apa

Re: ComplexPhraseQueryParser (Expanded Form and Boosting)

2010-02-01 Thread Mark Harwood
Try call rewrite on the query object to expand then call tostring on the result. Cheers, Mark - On 1 Feb 2010, at 21:32, "Haghighi, Nariman" wrote: > We are relying on the ComplexPhraseQueryParser for some impressive > matching capabilities. > > Of concern is that Wildcard Queries,

ComplexPhraseQueryParser (Expanded Form and Boosting)

2010-02-01 Thread Haghighi, Nariman
We are relying on the ComplexPhraseQueryParser for some impressive matching capabilities. Of concern is that Wildcard Queries, of the form "quality operations providing quality food services job requirements: click here to apply for this job*", for instance, take 2-5 seconds to execute and requ