diff options
| author | jiangxingbo <jiangxb1987@gmail.com> | 2017-01-18 19:13:01 +0800 |
|---|---|---|
| committer | Wenchen Fan <wenchen@databricks.com> | 2017-01-18 19:13:01 +0800 |
| commit | f85f29608de801d7cacc779a77c8edaed8124acf (patch) | |
| tree | 6bb10b7ee796baacbd085dbd202d2372ec107bda /core/src/main | |
| parent | 17ce0b5b3f6a825fc77458bc8608cece1a6019c7 (diff) | |
| download | spark-f85f29608de801d7cacc779a77c8edaed8124acf.tar.gz spark-f85f29608de801d7cacc779a77c8edaed8124acf.tar.bz2 spark-f85f29608de801d7cacc779a77c8edaed8124acf.zip | |
[SPARK-19024][SQL] Implement new approach to write a permanent view
## What changes were proposed in this pull request?
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 column names of the query plan, and current database to CatalogTable. Permanent views created by this approach can be resolved by current view resolution approach.
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.
Major changes of this PR:
1. Generate the view-specific properties(e.g. view default database, view query output column names) during permanent view creation and store them as properties in the CatalogTable;
2. Update the commands `CreateViewCommand` and `AlterViewAsCommand`, get rid of SQL generation from them.
## How was this patch tested?
Existing tests.
Author: jiangxingbo <jiangxb1987@gmail.com>
Closes #16613 from jiangxb1987/view-write-path.
Diffstat (limited to 'core/src/main')
0 files changed, 0 insertions, 0 deletions