[SPARK-43203] Fix DROP table behavior in session catalog

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.2, 3.5.0
• Component/s: SQL
• Labels: pull-request-available
• Assignee: Jia Fan
• Reporter: Anton Okolnychyi
• Created: 19/Apr/23 19:16
• Updated: 11/Sep/23 13:48
• Resolved: 19/Jun/23 12:43

Description

DROP table behavior is not working correctly in 3.4.0 because we always invoke V1 drop logic if the identifier looks like a V1 identifier. This is a big blocker for external data sources that provide custom session catalogs.

See here for details.

Issue Links

• is caused by: SPARK-40425 DROP TABLE does not need to do table lookup
• links to: [Github] Pull Request #41348 (Hisoka-X)
• links to: [Github] Pull Request #41765 (Hisoka-X)
• links to: GitHub Pull Request #41765