[
https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-6308:
--------------------------------
Attachment: LUCENE-6308-changeapi.patch
I really like this patch, it means spans have real cost() support, two-phase
iteration, etc.
I created an alternative version of it, where we just break the low level Spans
api with your changes and we don't have to deprecate all the spans (since you
have replacements for every query).
So this version is less invasive and just "fixes" spans with your new code.
I think this is ok? The classes are documented expert, and for most users, just
using the queries we have, there are no changes that will impact them (its all
internals). Queries will just get faster. Otherwise they have to change parsers
and so on to generate the new queries.
> 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.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]
