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

Xin Wu commented on SPARK-18727:
--------------------------------

[~ekhliang] I see. I will try to support ALTER TABLE SCHEMA. Also this is 
similar or the same as ALTER TABLE REPLACE COLUMNS, which is documented as 
unsupported Hive feature in SqlBase.q4.. Do we have preference which one to use?

> Support schema evolution as new files are inserted into table
> -------------------------------------------------------------
>
>                 Key: SPARK-18727
>                 URL: https://issues.apache.org/jira/browse/SPARK-18727
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.1.0
>            Reporter: Eric Liang
>            Priority: Critical
>
> Now that we have pushed partition management of all tables to the catalog, 
> one issue for scalable partition handling remains: handling schema updates.
> Currently, a schema update requires dropping and recreating the entire table, 
> which does not scale well with the size of the table.
> We should support updating the schema of the table, either via ALTER TABLE, 
> or automatically as new files with compatible schemas are appended into the 
> table.
> cc [~rxin]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to