lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Resolved] (LUCENE-7575) UnifiedHighlighter: add requireFieldMatch=false support
Date Mon, 05 Dec 2016 21:27:58 GMT


David Smiley resolved LUCENE-7575.
       Resolution: Fixed
    Fix Version/s: 6.4

Thank _you_.

I was thinking a bit more about the wastefulness of re-creating SpanQueries with different
field that are otherwise identical. Some day we could refactor out from WSTE a Query ->
SpanQuery conversion utility that furthermore allows you to re-target the field.  With that
in place, we could avoid the waste for PhraseQuery and MultiPhraseQuery -- the most typical
position-sensitive queries.

> UnifiedHighlighter: add requireFieldMatch=false support
> -------------------------------------------------------
>                 Key: LUCENE-7575
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/highlighter
>            Reporter: David Smiley
>            Assignee: David Smiley
>             Fix For: 6.4
>         Attachments: LUCENE-7575.patch, LUCENE-7575.patch, LUCENE-7575.patch
> The UnifiedHighlighter (like the PostingsHighlighter) only supports highlighting queries
for the same fields that are being highlighted.  The original Highlighter and FVH support
loosening this, AKA requireFieldMatch=false.

This message was sent by Atlassian JIRA

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

View raw message