You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2022/02/17 12:45:00 UTC
[GitHub] [lucene] wjp719 opened a new pull request #688: PostingsEnum supports to return current index of postings
wjp719 opened a new pull request #688:
URL: https://github.com/apache/lucene/pull/688
PostingsEnum supports to return current index of postings
As we known, the docId list in .doc is like an array of integer, every element of this array is a docId, when we call nextDoc or advance method, it will move to another element of this array. this pr support to return current index of the element in the posting list. We can use method to find the diff value when we call advance, the diff value means we skip how many doc in this docId list.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene] jpountz commented on pull request #688: LUCENE-10425：PostingsEnum supports to return current index of postings
Posted by GitBox <gi...@apache.org>.
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 I'd like to think a bit more about what problems this would be solving. I'll leave some thoughts on the JIRA issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene] wjp719 commented on pull request #688: LUCENE-10425：PostingsEnum supports to return current index of postings
Posted by GitBox <gi...@apache.org>.
wjp719 commented on pull request #688:
URL: https://github.com/apache/lucene/pull/688#issuecomment-1043888635
@msokolov Hi, I describe a use case in this issue https://issues.apache.org/jira/browse/LUCENE-10425 , thanks a lot
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene] msokolov commented on pull request #688: LUCENE-10425：PostingsEnum supports to return current index of postings
Posted by GitBox <gi...@apache.org>.
msokolov commented on pull request #688:
URL: https://github.com/apache/lucene/pull/688#issuecomment-1043123035
I'm concerned exposing this could limit future implementations by requiring them to support it. Do you have a proposed use case that would justify needing to add this? Maybe post to java-user@lucene.apache.org explaining the use case?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene] jpountz commented on pull request #688: LUCENE-10425：PostingsEnum supports to return current index of postings
Posted by GitBox <gi...@apache.org>.
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 be able to get the current index in constant time like the current postings can, we'd have to count all one bits.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org