You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2020/05/23 04:54:00 UTC
[jira] [Commented] (SOLR-12901) Make UnifiedHighlighter the default
[ https://issues.apache.org/jira/browse/SOLR-12901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114536#comment-17114536 ]
David Smiley commented on SOLR-12901:
-------------------------------------
{{hl.preserveMulti}} is not supported yet, and is possibly more important than some of the others for multi-value fields. It's not too hard if we also assume {{hl.bs.type=WHOLE}} for this case, which makes sense to me any way.
> Make UnifiedHighlighter the default
> -----------------------------------
>
> Key: SOLR-12901
> URL: https://issues.apache.org/jira/browse/SOLR-12901
> Project: Solr
> Issue Type: Improvement
> Components: highlighter
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Fix For: master (9.0)
>
>
> I think the UnifiedHighlighter should be the default in 8.0. It's faster and more accurate than alternatives.
> The original highlighter however has some benefits:
> * Different passage/snippet delineation options; somewhat more flexible. Though no i18n BreakIterator based one.
> * Seems to handle some "special" Queries and/or QueryParsers by default better -- namely SurroundQParser. Though SOLR-12895 will address this UH issue.
> * Considers boosts in the query when computing a passage score
> * hl.alternateField, hl.maxAlternateFieldLength, hl.highlightAlternate options. Instead the UH has hl.defaultSummary boolean
> See https://builds.apache.org/job/Solr-reference-guide-master/javadoc/highlighting.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org