You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Chris Troullis (JIRA)" <ji...@apache.org> on 2019/08/15 18:21:00 UTC
[jira] [Created] (SOLR-13699) maxChars no longer working as
designed on CopyField
Chris Troullis created SOLR-13699:
-------------------------------------
Summary: maxChars no longer working as designed on CopyField
Key: SOLR-13699
URL: https://issues.apache.org/jira/browse/SOLR-13699
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 8.1.1, 8.2, 8.1, 8.0, 7.7.2, 7.7.1, 7.7, 8.0.1, 7.7.3, 8.1.2
Reporter: Chris Troullis
We recently upgraded from Solr 7.3 to 8.1, and noticed that the maxChars property on a copy field is no longer functioning as designed. Per the most recent documentation it looks like there have been no intentional changes as to the functionality of this property, so I assume this is a bug.
In debugging the issue, it looks like the bug was caused by SOLR-12992. In DocumentBuilder where the maxChar limit is applied, it first checks if the value is instanceof String. As of SOLR-12992, string values are now coming in as ByteArrayUtf8CharSequence (unless they are above a certain size as defined by JavaBinCodec.MAX_UTF8_SZ), so they are failing the instanceof String check, and the maxChar truncation is not being applied.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org