[jira] [Resolved] (SPARK-52417) Simplify Table properties handling in View Schema Evolution Mode

["Gengliang Wang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-52417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gengliang Wang resolved SPARK-52417.
------------------------------------
    Fix Version/s: 4.1.0
       Resolution: Fixed

Issue resolved by pull request 51107
[https://github.com/apache/spark/pull/51107]

> Simplify Table properties handling in View Schema Evolution Mode
> ----------------------------------------------------------------
>
>                 Key: SPARK-52417
>                 URL: https://issues.apache.org/jira/browse/SPARK-52417
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 4.0.0
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.1.0
>
>
> When a View is created, ex CREATE VIEW v (a1, a2) AS select c1, c2, it needs to save both set of columns (alias and query output).
> It saves the alias as the View Schema, and the query output as a table property like (c1, 0) (c2, 1)
> In the new Schema Evolution mode, we never allow the alias (so, view schema == view query output schema).  Every time we detect schema change, we sync the view's schema with view query schema, keeping the invariant.
> So we can simplify the update in Schema Evolution mode to not update the table properties, and do not use them where they are currently used, in describe, etc..



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