Ah - that's useful to know. Although in that case I'd suggest that the
sensible thing for Luke to do would be to either remove the boost field,
or show it as "unavailable", instead of (misleadingly) displaying it as
1.0... 

Cheers,

Tim.

-----Original Message-----
From: Andrzej 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 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 functionality of
> Lucene appears to be correct. 
>   

This is not a bug or incompatibility - it's the way the boost values are

stored in the index. Once the index is written down, the original boost 
values per field and per doc cannot be retrieved, because they are 
calculated into so called "fieldNorm" values.

-- 
Best regards,
Andrzej Bialecki     <><
 ___. ___ ___ ___ _ _   __________________________________
[__ || __|__/|__||\/|  Information Retrieval, Semantic Web
___|||__||  \|  ||  |  Embedded Unix, System Integration
http://www.sigram.com  Contact: info at sigram dot com



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




********************************************************************************
The information contained in this email message may be confidential. If you are 
not the intended recipient, any use, interference with, disclosure or copying 
of this material is unauthorised and prohibited. Although this message and any 
attachments are believed to be free of viruses, no responsibility is accepted 
by Informa for any loss or damage arising in any way from receipt or use 
thereof.  Messages to and from the company are monitored for operational 
reasons and in accordance with lawful business practices. 
If you have received this message in error, please notify us by return and 
delete the message and any attachments.  Further enquiries/returns can be sent 
to [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to