[
https://issues.apache.org/jira/browse/SPARK-42683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-42683.
---------------------------------
Fix Version/s: 3.5.0
Resolution: Fixed
Issue resolved by pull request 40300
[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
> Fix For: 3.5.0
>
>
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
