score *= normDecoder[norms[doc] & 0xFF];// normalize for
field
If we're talking NORMS_IN_FREQ, then you'd replace that line with
one call to getBoost() against the TermDocs. (or maybe getNorm?
getMultiplier?)
I'll start there.
Considering I don't have to worry about any index f
[
http://issues.apache.org/jira/browse/LUCENE-503?page=comments#action_12377071 ]
Daniel Naber commented on LUCENE-503:
-
Thanks for your contribution. We're currently preparing Lucene 2.0 and as
feature updates are only planned for the release after 2.0
On 4/28/06, Doug Cutting <[EMAIL PROTECTED]> wrote:
Another complication is determining whether deletions have changed. We
don't have a per-segment version number. We could either add a version
to the segment (perhaps even in the deletions file)
Deletions (.del) --> ByteCount,BitCount,Bits
By
I think one of two things need to happen to the SegmentReader class.
Either make the 'segment' variable protected, or make the the initialize()
method protected.
Without this, subclassing SegmentReader is impossible, since there is no way
for the derived class to know what segment it is working w
On Apr 29, 2006, at 12:40 AM, Marvin Humphrey wrote:
One file, the "PostingsFile", which merges the FreqFile, ProxFile,
and Boost/Norm for each posting into a single contiguous block,
with an eye towards aggressively minimizing disk seeks.
Interpolating the positions between the Freqs is in
The code is filled with string equality code using == rather than
equals(). I honestly don't think it saves a single clock tick as the
JIT takes care of it when the first line of code in the equals method
is if (this == that) return true;
Please correct me if I'm wrong.
I can commit to do
--- karl wettin <[EMAIL PROTECTED]> wrote:
> The code is filled with string equality code using
> == rather than
> equals(). I honestly don't think it saves a single
> clock tick as the
> JIT takes care of it when the first line of code in
> the equals method
> is if (this == that) return tr
