Eh yeah. I remember reading that. The boost is calculated at indexing
time.
That didn't even click. Thanks.
Andrzej Bialecki wrote:
[EMAIL PROTECTED] wrote:
I'm pretty sure this is a bug or incompatibility with Luke - I'm using
boosted documents, and I seem to remember that Luke reported e
zej Bialecki [mailto:[EMAIL PROTECTED]
Sent: 23 January 2006 19:07
To: java-user@lucene.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: Boost value and LUKE
[EMAIL PROTECTED] wrote:
> I'm pretty sure this is a bug or incompatibility with Luke - I'm using
> boosted documents, and I
[EMAIL PROTECTED] wrote:
I'm pretty sure this is a bug or incompatibility with Luke - I'm using
boosted documents, and I seem to remember that Luke reported everything
as 1.0, even though my test applications showed things correctly.
The boost in the final app is working fine, so the functiona
rt [mailto:[EMAIL PROTECTED]
Sent: 23 January 2006 17:48
To: java-user@lucene.apache.org
Subject: Boost value and LUKE
Hello All,
I am testing the boost value within the latest version of Lucene and I'm
inspecting the results through Luke.
For each FIELD that I want to boost I use the
appears to be correct.
Cheers,
Tim.
-Original Message-
From: Don Vaillancourt [mailto:[EMAIL PROTECTED]
Sent: 23 January 2006 17:48
To: java-user@lucene.apache.org
Subject: Boost value and LUKE
Hello All,
I am testing the boost value within the latest version of Lucene and I'm
Hello All,
I am testing the boost value within the latest version of Lucene and I'm
inspecting the results through Luke.
For each FIELD that I want to boost I use the setBoost method. And
everything looks good. But Luke is refusing to exposure the boost value
and keeps returning 1.0 for th
