oug Cutting [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 5:10 PM
To: java-user@lucene.apache.org
Subject: Re: PerFieldSimilarity
Robichaud, Jean-Philippe wrote:
> How cool, I did not knew that... that may help me... If I understand you
> correctly, I can create a boolean que
Robichaud, Jean-Philippe wrote:
How cool, I did not knew that... that may help me... If I understand you
correctly, I can create a boolean query where each "clause" use a different
similarity ?
Yes. That would look something like:
BooleanQuery booleanQuery = new BooleanQuery();
TermQuery clause1
java-user@lucene.apache.org
Subject: Re: PerFieldSimilarity
Robichaud, Jean-Philippe wrote:
> Again, I can change
> the similarity of the reader at run-time and issue specific queries,
summing
> the score myself, but that is pretty inefficient.
You can also specify a Similarity implementation
Robichaud, Jean-Philippe wrote:
Again, I can change
the similarity of the reader at run-time and issue specific queries, summing
the score myself, but that is pretty inefficient.
You can also specify a Similarity implementation per Query node in a
complex query, e.g.:
BooleanQuery query = new Boo
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 03, 2005 7:40 PM
To: java-user@lucene.apache.org
Subject: Re: PerFieldSimilarity
On May 3, 2005, at 5:57 PM, Robichaud, Jean-Philippe wrote:
> Hi Everyone,
>
> I've been searching the archive without success
On May 3, 2005, at 5:57 PM, Robichaud, Jean-Philippe wrote:
Hi Everyone,
I've been searching the archive without success to answer this one:
is it
possible to specify one similarity class per field, just like we
can do with
an analyzer ? I know I can change the similarity of the searcher,
bu
Hi Everyone,
I've been searching the archive without success to answer this one: is it
possible to specify one similarity class per field, just like we can do with
an analyzer ? I know I can change the similarity of the searcher, but that
restrict me to break some complex queries into different