[jira] [Resolved] (SPARK-19024) Implement new approach to write a permanent view

["Wenchen Fan (JIRA)" <ji...@apache.org>]

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

Wenchen Fan resolved SPARK-19024.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0

> Implement new approach to write a permanent view
> ------------------------------------------------
>
>                 Key: SPARK-19024
>                 URL: https://issues.apache.org/jira/browse/SPARK-19024
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>            Reporter: Jiang Xingbo
>            Assignee: Jiang Xingbo
>             Fix For: 2.2.0
>
>
> On CREATE/ALTER a view, it's no longer needed to generate a SQL text string from the LogicalPlan, instead we store the SQL query text、the output schema of the LogicalPlan, and current database to CatalogTable. The new view resolution approach will be able to resolve the view.
> The main advantage includes:
> 	1. If you update an underlying view, the current view also gets updated;
> 	2. That gives us a change to get ride of SQL generation for operators.
> Should bring in the following changes:
> 	1. Add new params to `CatalogTable`, that represents the SQL query text、 the output schema of the LogicalPlan, and current database, on the time when the view is created;
> 	2. Update the commands `CreateViewCommand` and `AlterViewAsCommand`, get rid of SQL generation in them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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