You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2025/11/10 21:01:00 UTC
[jira] [Updated] (SPARK-52991) Implement MERGE INTO with SCHEMA EVOLUTION for V2 DataSource
[ https://issues.apache.org/jira/browse/SPARK-52991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-52991:
----------------------------------
Parent Issue: SPARK-54274 (was: SPARK-51166)
> Implement MERGE INTO with SCHEMA EVOLUTION for V2 DataSource
> ------------------------------------------------------------
>
> Key: SPARK-52991
> URL: https://issues.apache.org/jira/browse/SPARK-52991
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 4.1.0
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> https://issues.apache.org/jira/browse/SPARK-47627 already add the syntax for MERGE WITH SCHEMA EVOLUTION INTO. to support schema evolution if the SOURCE table has different schema than TARGET table.
> However, this require some external Spark extension to make a custom merge plan, and is not used natively by Spark when making Merge plan.
> We should honor the syntax when Spark makes the Merge plan for data source that support it (currently V2 Data Sources)
--
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