[
https://issues.apache.org/jira/browse/HIVE-17008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075790#comment-16075790
]
Dan Burkert commented on HIVE-17008:
------------------------------------
I'm observing these events through the [notification log
API|https://github.com/danburkert/hive/blob/master/metastore/if/hive_metastore.thrift#L1546-L1549].
Is it expected that {{ThriftHiveMetastore.get_next_notification}} returns
events for failed DDL operations? There isn't any way to discern whether or
not the event failed just from the {{NotificationEvent}} struct.
> Where exactly is the NPE - I assume somewhere down the notifyEvent stack ?
The NPE is thrown inside the notification event listener, because {{db}} can be
null on [this
line|https://github.com/apache/hive/blob/master/metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java?utf8=%E2%9C%93#L1139].
> 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)
