[
https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377972#comment-14377972
]
David Smiley commented on LUCENE-6308:
--------------------------------------
If we can't use Integer.MAX_VALUE as NO_MORE_POSITIONS then I propose we at
least pave the way for this to become the case for a future Lucene version. It
would be nice to have this for API consistency. In some of my work I have
abused positions to hold data but in doing so I didn't assume negative values
or Integer.MAX_VALUE would work. If I did and if it did work (I guess it
would?), I wouldn't expect that kind of usage abuse to necessarily be
compatible between minor Lucene releases as I already know I'm abusing
something outside of its intended use.
> SpansEnum, deprecate Spans
> --------------------------
>
> Key: LUCENE-6308
> URL: https://issues.apache.org/jira/browse/LUCENE-6308
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Affects Versions: Trunk
> Reporter: Paul Elschot
> Priority: Minor
> Attachments: LUCENE-6308-changeapi.patch,
> LUCENE-6308-changeapi.patch, LUCENE-6308-changeapi.patch, LUCENE-6308.patch,
> LUCENE-6308.patch, LUCENE-6308.patch, LUCENE-6308.patch, LUCENE-6308.patch,
> LUCENE-6308.patch
>
>
> An alternative for Spans that looks more like PositionsEnum and adds two
> phase doc id iteration
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
