[
https://issues.apache.org/jira/browse/LUCENE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744755#action_12744755
]
Mark Miller commented on LUCENE-1821:
-------------------------------------
I'd go with your solution then - I'd hate to expose doc base stuff on Searcher
or in Scorer (I'm not a big fan of gatherSubReaders being protected either).
Also, *we* can't put Searcher on a Weight - it needs to be serializable (though
you can if you don't need to count on that).
Where do you suggest we should place a warning that we havn't? I don't think we
ever intended to support the use of external ids.
I think your use case is fairly special, and I'm not sure we should expose per
segment stuff where we don't have to.
It is an interesting use case though - maybe someone else will chime in.
> Weight.scorer() not passed doc offset for "sub reader"
> ------------------------------------------------------
>
> Key: LUCENE-1821
> URL: https://issues.apache.org/jira/browse/LUCENE-1821
> 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: [email protected]
For additional commands, e-mail: [email protected]
