[SPARK-33290] REFRESH TABLE should invalidate cache even though the table itself may not be cached

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.7, 3.0.1, 3.1.0
• Fix Version/s: 2.4.8, 3.0.2, 3.1.0
• Component/s: SQL
• Labels: correctness
• Assignee: Chao Sun
• Reporter: Chao Sun
• Created: 29/Oct/20 19:21
• Updated: 20/Nov/20 23:19
• Resolved: 31/Oct/20 16:54

Description

For the following example:

CREATE TABLE t ...;
CREATE VIEW t1 AS SELECT * FROM t;
REFRESH TABLE t

If t is cached, t1 will be invalidated. However if t is not cached as above, the REFRESH command won't invalidate view t1. This could lead to incorrect result if the view is used later.

Issue Links

• relates to: SPARK-33311 Improve semantics for REFRESH TABLE
• links to: [Github] Pull Request #30187 (sunchao)
• links to: [Github] Pull Request #30187 (sunchao)
• links to: [Github] Pull Request #30215 (sunchao)
• links to: [Github] Pull Request #30256 (sunchao)
• links to: [Github] Pull Request #30256 (sunchao)