You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2023/03/06 16:08:00 UTC

[jira] [Commented] (SPARK-42683) Automatically rename metadata columns that conflict with data schema columns

    [ https://issues.apache.org/jira/browse/SPARK-42683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697017#comment-17697017 ] 

Apache Spark commented on SPARK-42683:
--------------------------------------

User 'ryan-johnson-databricks' has created a pull request for this issue:
https://github.com/apache/spark/pull/40300

> Automatically rename metadata columns that conflict with data schema columns
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-42683
>                 URL: https://issues.apache.org/jira/browse/SPARK-42683
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 3.3.2, 3.4.0
>            Reporter: Ryan Johnson
>            Priority: Major
>
> Today, if a datasource already has a column called `_metadata`, queries cannot access the file-source metadata column that normally carries that name. We can address this conflict with two changes to metadata column handling:
>  # Automatically rename any metadata column whose name conflicts with a data schema column
>  # Add a facility to reliably find metadata columns by their original/logical name, even if they were renamed.



--
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