I will try to debug it On Fri, Sep 9, 2011 at 1:20 AM, Koji Sekiguchi <[email protected]> wrote: > Sorry about that > I'm out of office till tonight pls feel free to revert > Best regards > > Koji Sekiguchi from mobile > > > On 2011/09/09, at 14:03, "Chris Male (JIRA)" <[email protected]> wrote: > >> >> [ >> https://issues.apache.org/jira/browse/LUCENE-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >> ] >> >> Chris Male reopened LUCENE-1889: >> -------------------------------- >> >> >> Solr's build is broken by these changes it seems. >> >>> 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 >>> Assignee: Koji Sekiguchi >>> Priority: Minor >>> Fix For: 3.5, 4.0 >>> >>> Attachments: LUCENE-1889.patch, 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] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
-- lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
