[
https://issues.apache.org/jira/browse/LUCENE-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-5415:
--------------------------------
Attachment: LUCENE-5415.patch
Here's a prototype. just has one trivial test (needs some more before
committing), so the usual warnings apply. But it does not change the default
behavior at all, or require any changes to the main loop of the highlighting
algorithm.
> 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
>
>
> 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]
