lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SOLR-10018) hl.maxAnalyzedChars should have consistent default across highlighters
Date Thu, 02 Feb 2017 18:56:52 GMT

     [ https://issues.apache.org/jira/browse/SOLR-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Smiley resolved SOLR-10018.
---------------------------------
    Resolution: Fixed

The problem is unlikely to happen again since the patch establishes a highlighter default
in SolrHighlighter.java instead of referring to a constant at the Lucene layer per-highlighter
impl.

> hl.maxAnalyzedChars should have consistent default across highlighters
> ----------------------------------------------------------------------
>
>                 Key: SOLR-10018
>                 URL: https://issues.apache.org/jira/browse/SOLR-10018
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: highlighter
>    Affects Versions: 6.4
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Minor
>             Fix For: 6.5
>
>         Attachments: SOLR_10018__default_hl_maxAnalyazedChars.patch, SOLR-10018-test.patch
>
>
> I see no reason why hl.maxAnalyzedChars should have different defaults per highlighter
implementation. The default is typically 51,200 but for the UnifiedHighlighter and PostingsHighlighter
it's 10,000. This could easily lead to an unexpected lack of highlights that you expect to
see when trying the UH.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message