[
https://issues.apache.org/jira/browse/LUCENE-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099715#comment-13099715
]
Mike Sokolov commented on LUCENE-1889:
--------------------------------------
Koji - back in June, you expressed some interest in this; are you still
interested / do you have time to review the patch? I think it is as good a
solution as one can wish for in the context of FVH. Possibly LUCENE-2878 will
end up as something better, but it is a longer-term project I think with a lot
of work left to be done; in the meantime this would offer a good way to extend
FVH support to a broader range of queries. This'll be my last nudge :)
> FastVectorHighlighter: support for additional queries
> -----------------------------------------------------
>
> Key: LUCENE-1889
> URL: https://issues.apache.org/jira/browse/LUCENE-1889
> Project: Lucene - Java
> Issue Type: Wish
> Components: modules/highlighter
> Reporter: Robert Muir
> Priority: Minor
> Attachments: LUCENE-1889.patch, LUCENE-1889.patch
>
>
> I am using fastvectorhighlighter for some strange languages and it is working
> well!
> One thing i noticed immediately is that many query types are not highlighted
> (multitermquery, multiphrasequery, etc)
> Here is one thing Michael M posted in the original ticket:
> {quote}
> I think a nice [eventual] model would be if we could simply re-run the
> scorer on the single document (using InstantiatedIndex maybe, or
> simply some sort of wrapper on the term vectors which are already a
> mini-inverted-index for a single doc), but extend the scorer API to
> tell us the exact term occurrences that participated in a match (which
> I don't think is exposed today).
> {quote}
> Due to strange requirements I am using something similar to this (but
> specialized to our case).
> I am doing strange things like forcing multitermqueries to rewrite into
> boolean queries so they will be highlighted,
> and flattening multiphrasequeries into boolean or'ed phrasequeries.
> I do not think these things would be 'fast', but i had a few ideas that might
> help:
> * looking at contrib/highlighter, you can support FilteredQuery in flatten()
> by calling getQuery() right?
> * maybe as a last resort, try Query.extractTerms() ?
--
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]
