[
https://issues.apache.org/jira/browse/LUCENE-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554756#comment-14554756
]
Alan Woodward commented on LUCENE-6494:
---------------------------------------
Yeah, it's NearSpansOrdered that makes everything complicated, because by the
time you call collect() its child Spans have moved on. So you need to either
have just a generic collector type, or pass the collector type to the
NearSpansOrdered constructor and have a way of creating a buffered collector
from that, which leads to the overcomplicated generics that Robert didn't like.
There might be a way of doing this by passing a SpanCollector to the SpanWeight
somehow? And just doing some ugly brute-force casting in replay(), risking the
ire of the Generics Policeman. But in the meantime, please do try this API out
- feedback from people other than me who are using it will be very useful!
> Make PayloadSpanUtil apply to other postings information
> --------------------------------------------------------
>
> Key: LUCENE-6494
> URL: https://issues.apache.org/jira/browse/LUCENE-6494
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Fix For: 5.2
>
> Attachments: LUCENE-6494.patch, LUCENE-6494.patch, LUCENE-6494.patch,
> LUCENE-6494.patch
>
>
> With the addition of SpanCollectors, we can now get arbitrary postings
> information from SpanQueries. PayloadSpanUtil does some rewriting to convert
> non-span queries into SpanQueries so that it can collect payloads. It would
> be good to make this more generic, so that we can collect any postings
> information from any query (without having to make invasive changes to
> already optimized Scorers, etc).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
