You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2017/03/01 07:00:51 UTC
[jira] [Created] (LUCENE-7719) UnifiedHighlighter doesn't handle
some AutomatonQuery's with multi-byte chars
David Smiley created LUCENE-7719:
------------------------------------
Summary: UnifiedHighlighter doesn't handle some AutomatonQuery's with multi-byte chars
Key: LUCENE-7719
URL: https://issues.apache.org/jira/browse/LUCENE-7719
Project: Lucene - Core
Issue Type: Bug
Components: modules/highlighter
Reporter: David Smiley
In MultiTermHighlighting, a CharacterRunAutomaton is being created that takes the result of AutomatonQuery.getAutomaton that in turn is byte oriented, not character oriented. For ASCII terms, this is safe but it's not for multi-byte characters. This is most likely going to rear it's head with a WildcardQuery, but due to special casing in MultiTermHighlighting, PrefixQuery isn't affected. Nonetheless it'd be nice to get a general fix in so that MultiTermHighlighting can remove special cases for PrefixQuery and TermRangeQuery (both subclass AutomatonQuery).
AFAICT, this bug was likely in the PostingsHighlighter since inception.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org