[
https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341463#comment-14341463
]
Paul Elschot commented on LUCENE-6308:
--------------------------------------
bq. if we get it in shape
The idea was to have this ready, including two phase iteration, for 6.0, but I
did not yet find the possibility to indicate that in jira.
bq. with api breaks
Developing it this way has the advantage that nothing breaks, and that testing
is easy by duplicating the test code and then renaming the tested queries.
The disadvantage is that to see the actual code changes one needs a diff over a
rename.
I have positional join (custom) queries at LUCENE-5627 and these would also
benefit. I would prefer to have a deprecation time window to use SpansEnum
there.
Also renaming is simple enough to take the advantage.
Anyway, once this is ready we can still decide to use the existing names and
break the api.
> SpansEnum, deprecate Spans
> --------------------------
>
> Key: LUCENE-6308
> URL: https://issues.apache.org/jira/browse/LUCENE-6308
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Reporter: Paul Elschot
> Priority: Minor
> Attachments: LUCENE-6308.patch
>
>
> An alternative for Spans that looks more like PositionsEnum.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
