lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Smith (JIRA)" <>
Subject [jira] Commented: (LUCENE-1821) Weight.scorer() not passed doc offset for "sub reader"
Date Wed, 19 Aug 2009 03:19:15 GMT


Tim Smith commented on LUCENE-1821:

on "internal lucene ids"

right now (2.4) i always know what docids map to what IndexReader (always the top level)
i don't have a problem breaking that assumption, as long as i have the context to map docids
between spaces (sub reader to top level and back (mabye even a couple more levels in between))

I opened this ticket soley because in the Scorer API there is no presented way to actually
do this mapping between spaces (short of the "hacks" i discussed way above)
I have no problem whatsoever in the changing of what "space" docids exist in, as long as i
can get to and from the top level to this space
I also have no problem if how to do this mapping changes between releases (as long as its

> Weight.scorer() not passed doc offset for "sub reader"
> ------------------------------------------------------
>                 Key: LUCENE-1821
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Search
>    Affects Versions: 2.9
>            Reporter: Tim Smith
> Now that searching is done on a per segment basis, there is no way for a Scorer to know
the "actual" doc id for the document's it matches (only the relative doc offset into the segment)
> If using caches in your scorer that are based on the "entire" index (all segments), there
is now no way to index into them properly from inside a Scorer because the scorer is not passed
the needed offset to calculate the "real" docid
> suggest having Weight.scorer() method also take a integer for the doc offset
> Abstract Weight class should have a constructor that takes this offset as well as a method
to get the offset
> All Weights that have "sub" weights must pass this offset down to created "sub" weights

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message