: IMHO it would be nice if Lucene's Similarity formula took the
: indexed-date of the document into account. Ideally as an optional
: setting, where the user can provide a date field as well.
It really wouldn't make sense to incorporate this into the Similarity
class.
: Some of the other searc
anism where you can add "feature requests" for Lucene?
>
>
> -Original Message-
> From: Dominik Bruhn [mailto:[EMAIL PROTECTED]
> Sent: Sunday, December 30, 2007 4:38 AM
> To: java-user@lucene.apache.org
> Subject: Re: Prioiritze new documents
>
> Hy,
> a solution came i
s age over time, they are less important
than the new ones.
Is JIRA the mechanism where you can add "feature requests" for Lucene?
-Original Message-
From: Dominik Bruhn [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 30, 2007 4:38 AM
To: java-user@lucene.apache.org
Subject
>
> I got a large index and when searching for a term I want the newer
> documents be at the begining of the result set. I dont need a real order
> by time but lucene should prioritze the newer documents.
> I got the time of the document creation as a index-field but it takes
> very long if I would
I think it is the case that Luke doesn't show the boosts, see
http://www.gossamer-threads.com/lists/lucene/java-user/32020?search_string=Luke%20boost%201;#32020
On Dec 30, 2007, at 7:38 AM, Dominik Bruhn wrote:
Hy,
a solution came into my mind:
Every document gets boosted by a integer which I
On Sun, Dec 30, 2007 at 02:32:14PM +0100, Daniel Naber wrote:
> Yes, it looks like a bug, at least in the javadoc. In FieldsReader, the
> document is created but setBoost() is never called. So calling getBoost is
> like calling get("field") on a field that isn't stored. Could you open an
> issue
On Sonntag, 30. Dezember 2007, Dominik Bruhn wrote:
> I already know this, but ALL documents got a bost of 1. The values
> should a least differ some how, shouldnt they?
Yes, it looks like a bug, at least in the javadoc. In FieldsReader, the
document is created but setBoost() is never called. So
On Sun, Dec 30, 2007 at 02:08:37PM +0100, Daniel Naber wrote:
> From the Javadoc of getBoost():
>
> Note: This value is not stored directly with the document in the index.
> Documents returned from IndexReader.document(int) and Hits.doc(int) may
> thus not have the same value present as when thi
On Sonntag, 30. Dezember 2007, Dominik Bruhn wrote:
> Although I set the Boost via doc.setBoost(value) for each document
> before writing it to the index it doesnt change anything. Even worse if
> I look at the index using Luke (Version 0.7.1) each document got a boost
> of 1 not of the value supp
Hy,
a solution came into my mind:
Every document gets boosted by a integer which I increment each time I
add a new document to the index. So the newer documents should get a
bigger boost than the older ones.
I tried it out and ran into a problem:
Although I set the Boost via doc.setBoost(value)
Hy,
I got a large index and when searching for a term I want the newer
documents be at the begining of the result set. I dont need a real order
by time but lucene should prioritze the newer documents.
I got the time of the document creation as a index-field but it takes
very long if I would force l
11 matches
Mail list logo
