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 2021/10/06 10:01:57 UTC
[GitHub] [lucene] jpountz commented on pull request #7: LUCENE-9820: Separate logic for reading the BKD index from logic to intersecting it
jpountz commented on pull request #7:
URL: https://github.com/apache/lucene/pull/7#issuecomment-935886196
> Currently we might return a size that is bigger that the number of points. Should we modified the method to return the exact number of points all the time or change the contract of the method?
Would it be easy/cheap to know the accurate count? If we change the contract, I'd prefer to change the name as well so that it cannot be confused with `PointValues#size` which needs to be accurate since we use it to check whether fields are single-valued for instance (by doing docCount == size).
--
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