[
https://issues.apache.org/jira/browse/LUCENE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065340#comment-13065340
]
Yonik Seeley commented on LUCENE-3314:
--------------------------------------
The javadoc of next says:
{code}
Returns the resulting term, or null if the end was hit (which means the enum
is unpositioned).
{code}
It doesn't say anything about the result of next() if the previous call
resulted in null, and the "unpositioned" verbiage would suggest a more
undefined state to me. If calling next() after null is returned is supported,
we should doc it (but this might add extra overhead/state to some
implementations?)
> TestNumericRangeQuery test failure
> ----------------------------------
>
> Key: LUCENE-3314
> URL: https://issues.apache.org/jira/browse/LUCENE-3314
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 4.0
> Reporter: Robert Muir
>
> https://builds.apache.org/view/G-L/view/Lucene/job/Lucene-trunk/1624/testReport/org.apache.lucene.search/TestNumericRangeQuery32/testEnum/
> ant test -Dtestcase=TestNumericRangeQuery32 -Dtestmethod=testEnum
> -Dtests.seed=-3603272894684698645:-1998239306864854687 -Dtests.multiplier=3
> -Dtests.nightly=true
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
