hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dere (JIRA)" <>
Subject [jira] [Commented] (HIVE-12304) "drop database cascade" needs to unregister functions
Date Wed, 04 Nov 2015 23:55:27 GMT


Jason Dere commented on HIVE-12304:


So this removes the registered functions for the database, on the client that drops the database.
This fixes the behavior for the client that runs the drop database command, including HS2
if the DB is dropped from HS2. But another HiveCLI client that has already loaded the functions
for this DB will still have the permanent functions in its FunctionRegistry if the DB is dropped
from a different HiveCLI client. But, this is probably the best we can do.

> "drop database cascade" needs to unregister functions
> -----------------------------------------------------
>                 Key: HIVE-12304
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 2.0.0
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>         Attachments: HIVE-12304.2.patch, HIVE-12304.patch
> 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.

This message was sent by Atlassian JIRA

View raw message