[ 
https://issues.apache.org/jira/browse/SPARK-34052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272333#comment-17272333
 ] 

Chao Sun commented on SPARK-34052:
----------------------------------

[~hyukjin.kwon] [~cloud_fan] do you think we should include this in 3.1.1? 
since we've changed how temp view work in SPARK-33142 it may be better to add 
this too to make it consistent.

> A cached view should become invalid after a table is dropped
> ------------------------------------------------------------
>
>                 Key: SPARK-34052
>                 URL: https://issues.apache.org/jira/browse/SPARK-34052
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 3.0.1, 3.1.0
>            Reporter: Chao Sun
>            Assignee: Chao Sun
>            Priority: Major
>             Fix For: 3.2.0, 3.1.2
>
>
> It seems a view doesn't become invalid after a DSv2 table is dropped or 
> replaced. This is different from V1 and may cause correctness issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to