You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Daniel Tenedorio (Jira)" <ji...@apache.org> on 2026/10/20 20:17:00 UTC
[jira] [Resolved] (SPARK-60244) Follow-up to SPARK-60108
[ https://issues.apache.org/jira/browse/SPARK-60244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Tenedorio resolved SPARK-60244.
--------------------------------------
Fix Version/s: 4.4.0
Resolution: Fixed
Issue resolved by pull request 59516
[https://github.com/apache/spark/pull/59516]
> Follow-up to SPARK-60108
> -------------------------
>
> Key: SPARK-60244
> URL: https://issues.apache.org/jira/browse/SPARK-60244
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 5.0.0, 4.4.0
> Reporter: Serge Rielau
> Assignee: Serge Rielau
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.4.0
>
>
> Follow-up to SPARK-60108 (PR apache/spark#59325), which added
> UNSUPPORTED_JSON_CHAR_VARCHAR_MAP_KEY for JSON CHAR/VARCHAR map keys. Align the
> parallel XML condition from SPARK-60103 to match. Two items, message/formatting
> only -- do NOT change XML behavior (XML keys last-win; mapKeyDedupPolicy is not
> applied):
> 1. Message wording. Make UNSUPPORTED_XML_CHAR_VARCHAR_MAP_KEY parallel to the
> richer JSON wording.
> - JSON (target style), common/utils/.../error/error-conditions.json:
> line 1: "The JSON object name <key> is not a valid key for the map key type <dataType>."
> line 2: "A CHAR key must match the declared length exactly and a VARCHAR key
> must not exceed it; keys are never padded or trimmed. Use a STRING
> map key to accept any name."
> - XML (current, to update):
> line 1: "XML map keys of CHAR or VARCHAR cannot be padded or trimmed."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org