[
https://issues.apache.org/jira/browse/HIVE-17008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075068#comment-16075068
]
Dan Burkert commented on HIVE-17008:
------------------------------------
Hi [~mohitsabharwal], here is a better diff of the patch:
https://github.com/danburkert/hive/commit/ec115a584c4b2b715f339458afc2bcbf353d1e47?w=1.
Since filing this bug / uploading the patch I've found that the HMS can fire
event listeners on almost any type of failed DDL operation: drop database,
create table, partitions, functions, indices, etc. The patch only fixes the
drop database case, but the fix is pretty much the same. It's not clear to me
what the designed behavior is, though. Are these just copy/pasted bugs, or is
it by design that the HMS notifies listeners for failed DDL operations?
> HiveMetastore.drop_database can return NPE if database does not exist
> ---------------------------------------------------------------------
>
> Key: HIVE-17008
> URL: https://issues.apache.org/jira/browse/HIVE-17008
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Dan Burkert
> Assignee: Dan Burkert
> Attachments: HIVE-17008.0.patch
>
>
> When dropping a non-existent database, the HMS will still fire registered
> {{DROP_DATABASE}} event listeners. This results in an NPE when the listeners
> attempt to deref the {{null}} database parameter.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
