[LUCENE-1889] FastVectorHighlighter: support for additional queries

• Type: Wish
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.5, 4.0-ALPHA
• Component/s: modules/highlighter
• Lucene Fields: New
• Assignee: Koji Sekiguchi
• Reporter: Robert Muir
• Created: 03/Sep/09 14:44
• Updated: 28/Aug/22 12:08
• Resolved: 13/Oct/11 12:11

Description

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:

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).

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() ?

Issue Links

• breaks: SOLR-7488 suspicious FVH init code in DefaultSolrHighlighter even when FVH should not be used
• relates to: LUCENE-2243 FastVectorHighlighter: support DisjunctionMaxQuery