[
https://issues.apache.org/jira/browse/LUCENE-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770811#comment-15770811
]
ASF subversion and git services commented on LUCENE-7601:
---------------------------------------------------------
Commit 30a52277dea16f4d15c40a0ec17f69076242496d in lucene-solr's branch
refs/heads/master from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=30a5227 ]
LUCENE-7601: Make DocIdMerger.next() unspecified when exhausted.
> Make DocIdMerger.next() unspecified when exhausted
> --------------------------------------------------
>
> Key: LUCENE-7601
> URL: https://issues.apache.org/jira/browse/LUCENE-7601
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-7601.patch
>
>
> Right now there is a comment saying {{NOTE: it's annoying that caller is
> allowed to call us again even after we returned null before}}, but when I
> throw an exception in that condition, no tests fail. So maybe we can get rid
> of this protection now and just make next() unspecified after exhaustion,
> like {{DocIdSetIterator}}?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
