[ https://issues.apache.org/jira/browse/LUCENE-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Harwood updated LUCENE-1999: --------------------------------- Attachment: matchflagger.patch > Match spotter for all query types > --------------------------------- > > Key: LUCENE-1999 > URL: https://issues.apache.org/jira/browse/LUCENE-1999 > Project: Lucene - Java > Issue Type: New Feature > Affects Versions: 2.9 > Reporter: Mark Harwood > Attachments: matchflagger.patch > > > Related to LUCENE-1929 and the current inability to highlight > NumericRangeQuery, spatial, cached term filters and other exotica. > This patch provides the ability to wrap *any* Query objects and record match > info as flags encoded in the overall document score. > Using this approach it would be possible to understand (and therefore > highlight) which fields matched clauses in a query. > The match encoding approach loses some precision in scores as noted here: > http://tinyurl.com/ykt8nx7 > Avoiding these precision issues would require a change to Lucene core to > record docId, score AND a matchFlag byte in ScoreDoc objects and collector > APIs. > This may be something we should consider. -- 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: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org