You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2016/12/21 22:12:58 UTC
[jira] [Created] (LUCENE-7601) Make DocIdMerger.next() unspecified
when exhausted
Adrien Grand created LUCENE-7601:
------------------------------------
Summary: 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
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@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org