[
https://issues.apache.org/jira/browse/LUCENE-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved LUCENE-7757.
----------------------------------
Resolution: Fixed
Fix Version/s: 7.5
LUCENE-8286 (WEIGHT_MATCHES flag to the UH) fixes this issue. Sure; it'd be
nice if the above points were addressed but this mechanism works. I know you'd
rather consume this via SOLR; I filed SOLR-12754 for adding this option. Just
now I have a test WIP and I see it's fixed. I think I'll keep that test at the
Solr layer since I'd rather not have the highlighter module depend on some new
module it doesn't already depend on.
> 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
> Fix For: 7.5
>
>
> 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]
