You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Gengliang Wang (Jira)" <ji...@apache.org> on 2026/06/26 05:06:00 UTC
[jira] [Resolved] (SPARK-57544) Rework column ID validation for nested fields in DSv2
[ https://issues.apache.org/jira/browse/SPARK-57544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gengliang Wang resolved SPARK-57544.
------------------------------------
Assignee: Anton Okolnychyi
Resolution: Fixed
Resolved in https://github.com/apache/spark/pull/56796/
> Rework column ID validation for nested fields in DSv2
> -----------------------------------------------------
>
> Key: SPARK-57544
> URL: https://issues.apache.org/jira/browse/SPARK-57544
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 4.2.0
> Reporter: Anton Okolnychyi
> Assignee: Anton Okolnychyi
> Priority: Major
> Labels: pull-request-available
>
> The original implementation detected dropped-and-re-added columns by comparing top-level Column.id() strings in a dedicated validateColumnIds pass, but this approach had no visibility into nested struct fields, array elements, or map keys/values. To work around this limitation, connectors had to encode nested field IDs into the top-level ID string (as demonstrated by ComposedColumnIdTableCatalog), placing an unreasonable burden on connector authors and making the feature fragile by design.
--
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