[
https://issues.apache.org/jira/browse/SPARK-18801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiang Xingbo updated SPARK-18801:
---------------------------------
Description:
We should be able to resolve a nested view. The main advantage is that if you
update an underlying view, the current view also gets updated.
The new approach should be compatible with older versions of SPARK/HIVE, that
means:
1. The new approach should be able to resolve the views that created by
older versions of SPARK/HIVE;
2. The new approach should be able to resolve the views that are
currently supported by SPARK SQL.
The new approach mainly brings in the following changes:
1. Add a new operator called `View` to keep track of the CatalogTable
that descripts the view, and the output attributes as well as the child of the
view;
2. Update the `ResolveRelations` rule to resolve the relations and
views, note that a nested view should be resolved correctly;
3. Add `AnalysisContext` to enable us to still support a view created
with CTE/Windows query.
was:
We should add a new operator called `View` to keep track of the database name
used on resolving a view. The analysis rule `ResolveRelations` should also be
updated.
After that change, we should be able to resolve a nested view.
> Add `View` operator to help resolve a view
> ------------------------------------------
>
> Key: SPARK-18801
> URL: https://issues.apache.org/jira/browse/SPARK-18801
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Reporter: Jiang Xingbo
>
> We should be able to resolve a nested view. The main advantage is that if you
> update an underlying view, the current view also gets updated.
> The new approach should be compatible with older versions of SPARK/HIVE, that
> means:
> 1. The new approach should be able to resolve the views that created by
> older versions of SPARK/HIVE;
> 2. The new approach should be able to resolve the views that are
> currently supported by SPARK SQL.
> The new approach mainly brings in the following changes:
> 1. Add a new operator called `View` to keep track of the CatalogTable
> that descripts the view, and the output attributes as well as the child of
> the view;
> 2. Update the `ResolveRelations` rule to resolve the relations and
> views, note that a nested view should be resolved correctly;
> 3. Add `AnalysisContext` to enable us to still support a view created
> with CTE/Windows query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]