[
https://issues.apache.org/jira/browse/LUCENE-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718827#action_12718827
]
Yonik Seeley commented on LUCENE-1685:
--------------------------------------
I've never gone deep into the highlighters, but I don't think we should
deprecate QueryScorer unless SpanScorer is a true superset (i.e. you can get
SpanScorer to act like QueryScorer if you want... minus any real bugs).
Highlighting is not an exact science. Given a query of
{code}"foo bar" -baz{code}
Not everyone will agree (and it will be application specific) exactly what
instances of foo, bar, and baz should be highlighted in the document. But I
agree that by default, we should try to only highlight what matches the query.
> Make the Highlighter use SpanScorer by default
> ----------------------------------------------
>
> Key: LUCENE-1685
> URL: https://issues.apache.org/jira/browse/LUCENE-1685
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 2.9
>
>
> I've always thought this made sense, but frankly, it took me a year to get
> the SpanScorer included with Lucene at all, so I was pretty much ready to
> move on after I it got in, rather than push for it as a default.
> I think it makes sense as the default in Solr as well, and I mentioned that
> back when it was put in, but alas, its an option there as well.
> The Highlighter package has no back compat req, but custom has been
> conservative - one reason I havn't pushed for this change before. Might be
> best to actually make the switch in 3? I could go either way - as is, I know
> a bunch of people use it, but I'm betting its the large minority. It has
> never been listed in a changes entry and its not in LIA 1, so you pretty much
> have to stumble upon it, and figure out what its for.
> I'll point out again that its just as fast as the standard scorer for any
> clause of a query that is not position sensitive. Position sensitive query
> clauses will obviously be somewhat slower to highlight, but that is because
> they will be highlighted correctly rather than ignoring position.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
