[HIVE-12304] "drop database cascade" needs to unregister functions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: Query Processor
• Target Version/s: 1.3.0
• Assignee: Aihua Xu
• Reporter: Aihua Xu
• Created: 30/Oct/15 17:17
• Updated: 14/Apr/16 11:43
• Resolved: 05/Nov/15 16:53

Description

Currently "drop database cascade" command doesn't unregister the functions under the database. If the functions are not unregistered, in some cases like "describe db1.func1" will still show the info for the function; or if the same database is recreated, "drop if exists db1.func1" will throw an exception since the function is considered existing from the registry while it doesn't exist in metastore.

Issue Links

• relates to: SPARK-14631 "drop database cascade" needs to unregister functions for HiveExternalCatalog
• links to: code review