You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Chao Sun (Jira)" <ji...@apache.org> on 2020/10/31 19:12:00 UTC
[jira] [Created] (SPARK-33311) Improve semantics for REFRESH TABLE
Chao Sun created SPARK-33311:
--------------------------------
Summary: Improve semantics for REFRESH TABLE
Key: SPARK-33311
URL: https://issues.apache.org/jira/browse/SPARK-33311
Project: Spark
Issue Type: Improvement
Components: SQL
Affects Versions: 3.0.1
Reporter: Chao Sun
Currently, the semantics for {{REFRESH TABLE t}} is not well defined for view (let's say {{view}}) that reference the table {{t}}:
1. If {{view}} is cached, the behavior is not well-defined. Should Spark invalidate the cache (current behavior) or recache it?
2. If {{view}} is a temporary view, currently refreshing {{t}} does not refresh {{view}} since it will just reuse the logical plan defined in the session catalog. This could lead to incorrect results.
I think we should clear define and document the behavior here, so that users won't get confused.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org