Github user dsmiley commented on the issue:
https://github.com/apache/lucene-solr/pull/105
_(I wrote this as you made your last comments, but rather than delete it
I'll comment any way)_
The documentation for `PostingsEnum.nextPosition()` states that calling it
more than `freq()` times is undefined. Thus it's quite valid to throw an
IllegalStateException.
> Btw, we've seen other needs for something like a CompositePostingsEnum
that abstracts over a set of terms, but since this is still internal, dropping
the house-keeping will also make this code do less.
I don't think I quite get what you're saying. By "other needs" do you mean
Bloomberg internally? If so, how would that relate this this one inside the
UH? Are you advocating a general purpose Multi-PosrtingsEnum? On the
latter... a highlighter wouldn't be where to introduce such a thing. There is
a `org.apache.lucene.index.MultiPostingsEnum` which I looked at while at the
Lucene hackday code sprint as it got my curiosity. Unfortunately, it doesn't
seem quite general purpose enough for us to use -- it demands a MultiTermsEnum
parent. Perhaps that could be improved to be useful without demanding a
MultiTermsEnum parent... but that seems like a separate issue.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
