[
https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340763#comment-14340763
]
Robert Muir commented on LUCENE-6308:
-------------------------------------
I really like the idea of bringing spans "up to speed" to support
approximations and other features.
I think this approach could fix performance issues with spans, because e.g.
then they are able to intersect with nextDoc()/advance() without implicitly
reading position(s).
This could be a really nice step. if we get it in shape, we could consider just
"fixing" the spans classes to use it, with api breaks. These wouldnt really
impact most users, only people writing custom queries. And those people
probably want to do it "the fast way"...
> 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]
