> ConstantScoreQuery would seem better, with the addition of the constant
> score value as a constructor argument.
OK, I changed the names to ConstantScoreQuery and ConstantScoreRangeQuery.
Should I add a constantScore field to the class, or just rely on the
boost (and have the user call setBoos
On Thursday 21 April 2005 17:41, Yonik Seeley wrote:
> OK, so as I said, my previous version of UnscoredRangeQuery that could
> work with any number of terms in the range had a problem - it could
> return duplicates if a doc had more than one term in the range.
>
> Here is how
OK, so as I said, my previous version of UnscoredRangeQuery that could
work with any number of terms in the range had a problem - it could
return duplicates if a doc had more than one term in the range.
Here is how I fixed it:
I hacked together an UnscoredQuery that takes a Filter (it's
e any other choice than a bitset to
remove the dups. At least I will be able to implement skipTo
though...
> For maximum performance, top level disjunctions are probably best done
> unordered, for example like the 1.4 BooleanScorer.
> From what I understood so far, this UnscoredRangeQuer
05, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> > OK, so I implemented an UnscoredRangeQuery we needed for use with
> > lucene 1.4.3. Seems to work fine for me, so I thought I would put it
> > out here to see what you guys think... (files attached)
> >
> > Would
Hi Yonik,
I'm interested, but I didn't see any files attached. Not sure if it's
at my end or the mailing list. Is there another way I can get these
files? Thanks
-Chris
On 4/14/05, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> OK, so I implemented an UnscoredRangeQuer
OK, so I implemented an UnscoredRangeQuery we needed for use with
lucene 1.4.3. Seems to work fine for me, so I thought I would put it
out here to see what you guys think... (files attached)
Would a cleaned up version be useful for some version of Lucene, or
will all the current work that Paul
