[
https://issues.apache.org/jira/browse/LUCENE-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881987#comment-13881987
]
Michael McCandless commented on LUCENE-5415:
--------------------------------------------
bq. Does telling them which MTQ matched really seem that important?
It seems like it may be useful? Again, I don't think it should block this
addition! It can be done later.
But e.g. with the lucene server (LUCENE-5376) when you search for "fast lucene"
and the content was "Lucene's PostingsHighlighter is fast", it returns this
JSON today:
{noformat}
{
"startOffset":0,
"endOffset":41,
"parts":[
{
"term":"lucene",
"text":"Lucene's"
},
" new PostingsHighlighter is ",
{
"term":"fast",
"text":"fast"
},
"."
]
}
{noformat}
Ie, for each "hit" in the snippet it tells you which term from the original
query "caused" that hit. So I thought it would also be useful somehow to know
which MTQ caused the hit too ... later!
> 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
>
>
> 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]
