Github user Timothy055 commented on the issue:
https://github.com/apache/lucene-solr/pull/105
I don't think there's a way to avoid keeping the position state,
unfortunately. The reason is that we can move one of the postings enums to the
next position, but then realize the next position for that term is behind the
position for a different term (and postings enum) that also matches the
wildcard. Then we'll update the top and switch to the next postings enum (by
offset now), but once it's exhausted or we switch back to the previous one from
interleaving the position is lost. :/ An alternative to avoid this would be
to change PostingsEnum to allow fetching of the currentPosition, then nearly
all the house keeping would go away.
---
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
