[
https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314220#comment-14314220
]
Alan Woodward commented on LUCENE-6226:
---------------------------------------
OK, let's back up a bit.
The primary purpose of adding this functionality to Scorer is to stop needing a
parallel Span*Query tree, and make positional queries combine with all our
other query types more sensibly. It would also be nice to replace the current
span scoring implementations with something that scores lazily.
So maybe a better place to start would be to open an issue that adds a
PositionFilterQuery that actually exercises this API? Then we can see how
clients interact with it, and see which changes are necessary and which are
just me guessing about what might be needed down the road.
> Allow TermScorer to expose positions, offsets and payloads
> ----------------------------------------------------------
>
> Key: LUCENE-6226
> URL: https://issues.apache.org/jira/browse/LUCENE-6226
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Fix For: Trunk, 5.1
>
> Attachments: LUCENE-6226.patch, LUCENE-6226.patch, LUCENE-6226.patch,
> LUCENE-6226.patch, LUCENE-6226.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
