[
https://issues.apache.org/jira/browse/SOLR-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850318#comment-15850318
]
ASF subversion and git services commented on SOLR-10018:
--------------------------------------------------------
Commit 1c7ae87f0cbc3440d022fecfbb1f980bf244f4ce in lucene-solr's branch
refs/heads/branch_6x from [~dsmiley]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1c7ae87 ]
SOLR-10018: default hl.maxAnalyazedChars to 51200 across all highlighters
(cherry picked from commit f5c6c3b)
> 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: [email protected]
For additional commands, e-mail: [email protected]
