[
https://issues.apache.org/jira/browse/SPARK-18389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651865#comment-15651865
]
Nattavut Sutyanyong commented on SPARK-18389:
---------------------------------------------
Yes. CREATE/ALTER is not the place where we should do extensive checking, maybe
syntax checking but leaving the relation name as unresolved relation.
Otherwise, you would need to do nested expansion of the objects in CREATE/ALTER.
Would my proposal fit well with the way Spark is implemented today?
> Disallow cyclic view reference
> ------------------------------
>
> Key: SPARK-18389
> URL: https://issues.apache.org/jira/browse/SPARK-18389
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Reporter: Reynold Xin
>
> The following should not be allowed:
> {code}
> CREATE VIEW testView AS SELECT id FROM jt
> CREATE VIEW testView2 AS SELECT id FROM testView
> ALTER VIEW testView AS SELECT * FROM testView2
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
