[
https://issues.apache.org/jira/browse/LUCENE-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066188#comment-13066188
]
Robert Muir commented on LUCENE-3318:
-------------------------------------
glancing at the branch, i would suggest dropping use of term vectors completely
here, and building the prototype to store the start/end offsets into the
payload for now. then the highlighter can translate positions into offsets via
the payload.
i think we should not use term vectors for highlighting... if the prototype
gets going we can then look at encoding (optionally) this offsets information
in the postings explicitly in parallel with positions more efficiently, e.g. in
ways that exploit that fact that in a majority of cases endOffset - startOffset
is going to be the same for every position of term X.
> Sketch out highlighting based on term positions / position iterators
> --------------------------------------------------------------------
>
> Key: LUCENE-3318
> URL: https://issues.apache.org/jira/browse/LUCENE-3318
> Project: Lucene - Java
> Issue Type: Sub-task
> Components: modules/highlighter
> Affects Versions: Positions Branch
> Reporter: Simon Willnauer
> Fix For: Positions Branch
>
>
> Spinn off from LUCENE-2878. Since we have positions on a large number of
> queries already in the branch is worth looking at highlighting as a real
> consumer of the API. A prototype is already committed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]