[ 
https://issues.apache.org/jira/browse/LUCENE-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869884#comment-16869884
 ] 

ASF subversion and git services commented on LUCENE-7757:
---------------------------------------------------------

Commit df4ebaf030cdc5aeeba527aab23febcb6dfc9601 in lucene-solr's branch 
refs/heads/branch_8x from David Wayne Smiley
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=df4ebaf ]

LUCENE-8848 LUCENE-7757 LUCENE-8492: UnifiedHighlighter.hasUnrecognizedQuery
The UH now detects that parts of the query are not understood by it.
When found, it highlights more safely/reliably.
Fixes compatibility with complex and surround query parsers.

(cherry picked from commit 54cc70127b22083198f1c44f83ccf4cdf769ac77)


> 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]

Reply via email to