[GitHub] [lucene] jpountz commented on pull request #688: LUCENE-10425:PostingsEnum supports to return current index of postings

2022-03-05 Thread GitBox
jpountz commented on pull request #688: URL: https://github.com/apache/lucene/pull/688#issuecomment-1059806742 Thinking through this a bit more, I imagine that this is the reason why you made this API optional. We still like the set the bar quite high to add new APIs to PostingsEnum so

[GitHub] [lucene] jpountz commented on pull request #688: LUCENE-10425:PostingsEnum supports to return current index of postings

2022-03-05 Thread GitBox
jpountz commented on pull request #688: URL: https://github.com/apache/lucene/pull/688#issuecomment-1059803598 The use-case makes sense to me, but like @msokolov I'm worried that this could limit future implementations. For instance if we were to encode postings as a bitset, we wouldn't