[
https://issues.apache.org/jira/browse/SPARK-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825746#comment-15825746
]
Apache Spark commented on SPARK-19024:
--------------------------------------
User 'jiangxb1987' has created a pull request for this issue:
https://github.com/apache/spark/pull/16613
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
