Github user dsmiley commented on the issue:
https://github.com/apache/lucene-solr/pull/105
Nevermind on `MultiPostingsEnum`. MPE assumes the PostingsEnum are for a
disjoint set of documents -- i.e. each PostingsEnum matches documents disjoint
from the others. This makes sense given it's use for a single view over
multiple segments. In our case we want what might be called a
MultiPositionsPostingsEnum or MultiOffsetsPostingsEnum or "Composite" instead
of "Multi" (synonymous, really). We merge the positions (yet we don't care
about the actual position #s; it's the other stuff we expose per-position).
BTW my code you merged had a "nocommit" to consider changing the class name.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
