lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-1889) FastVectorHighlighter: support for additional queries
Date Sat, 05 Sep 2009 12:45:57 GMT


Robert Muir commented on LUCENE-1889:

Jason, no but the high-level idea in concept is similar: re-run the query on single doc "mini-index"
to work a bit differently (specialized for highlighting)

if i had done it in a nice way I would have contributed something :)

> FastVectorHighlighter: support for additional queries
> -----------------------------------------------------
>                 Key: LUCENE-1889
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Wish
>          Components: contrib/*
>            Reporter: Robert Muir
>            Priority: Minor
> 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.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message