[ https://issues.apache.org/jira/browse/LUCENE-7575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ferenczi Jim updated LUCENE-7575: --------------------------------- Attachment: LUCENE-7575.patch Thanks David ! Here is a new patch to address your last comments. Now we have a FieldFilteringTermSet and extractTerms uses a simple HashSet. {quote} couldn't defaultFieldMatcher be initialized to non-null to match the same field? Then getFieldMatcher() would simply return it. {quote} Not as a Predicate<String> since the predicate is only on the candidate field name. We could use a BiPredicate<String, String> to always provide the current field name to the predicate but I find it simpler this way. > UnifiedHighlighter: add requireFieldMatch=false support > ------------------------------------------------------- > > Key: LUCENE-7575 > URL: https://issues.apache.org/jira/browse/LUCENE-7575 > Project: Lucene - Core > Issue Type: Improvement > Components: modules/highlighter > Reporter: David Smiley > Assignee: David Smiley > 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 (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org