[
https://issues.apache.org/jira/browse/LUCENE-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882173#comment-13882173
]
ASF subversion and git services commented on LUCENE-5415:
---------------------------------------------------------
Commit 1561451 from [~rcmuir] in branch 'dev/trunk'
[ https://svn.apache.org/r1561451 ]
LUCENE-5415: add multitermquery support to PostingsHighlighter
> Support wildcard & co in PostingsHighlighter
> --------------------------------------------
>
> Key: LUCENE-5415
> URL: https://issues.apache.org/jira/browse/LUCENE-5415
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/highlighter
> Reporter: Robert Muir
> Attachments: LUCENE-5415.patch, LUCENE-5415.patch, LUCENE-5415.patch,
> LUCENE-5415.patch, LUCENE-5415.patch
>
>
> PostingsHighlighter uses the offsets encoded in the postings lists for the
> terms to find query matches.
> As such, it isn't really suitable for stuff like wildcards for two reasons:
> 1. an expensive rewrite against the term dictionary (i think other
> highlighters share this problem)
> 2. accumulating data from potentially many terms (e.g. reading many postings)
> However, we could provide an option for some of these queries to work, but in
> a different way, that avoids these downsides.
> Instead we can just grab the Automaton representation of the queries, and
> match it against the content directly (which won't blow up).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
