[
https://issues.apache.org/jira/browse/LUCENE-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-7757:
---------------------------------
Fix Version/s: (was: 7.5)
I am mistaken. While the new HighlightFlags.WEIGHT_MATCHES is needed, it is
also necessary to override UnifiedHighlighter.getOptimizedOffsetSource to
ensure that NONE_NEEDED is never returned. So there's a work-around at the
Lucene level. Perhaps the root cause is the need for Lucene to have a better
Query visiting API and/or means of a way to extract automata in addition to the
terms it already extracts. Debatable.
See SOLR-12895 for possible Solr-level fixes.
> Unified highlighter does not highlight wildcard phrases correctly when
> ComplexPhraseQueryParser is used
> -------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-7757
> URL: https://issues.apache.org/jira/browse/LUCENE-7757
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/highlighter
> Affects Versions: 6.4
> Reporter: Bjarke Mortensen
> Assignee: David Smiley
> Priority: Major
>
> Given the text:
> "Kontraktsproget vil være dansk og arbejdssproget kan være dansk, svensk,
> norsk og engelsk"
> and the query:
> \{!complexphrase df=content_da\}("sve* no*")
> the unified highlighter (hl.method=unified) does not return any highlights.
> For reference, the original highlighter returns a snippet with the expected
> highlights:
> Kontraktsproget vil være dansk og arbejdssproget kan være dansk,
> <em>svensk</em>, <em>norsk</em> og
> Is this expected behaviour with the unified highlighter?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
