Subject: [jira] [Commented] (LUCENE-7601) Make
DocIdMerger.next() unspecified when exhausted




[
https://issues.apache.org/jira/browse/LUCENE-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768506#comment-15768506
]

Michael McCandless commented on LUCENE-7601:
--------------------------------------------

+1

> 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: dev-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxx



Programming list archiving by: Enterprise Git Hosting