[
https://issues.apache.org/jira/browse/HIVE-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268087#comment-14268087
]
Sushanth Sowmyan commented on HIVE-9174:
----------------------------------------
Actually, on last verification before commit, I notice one last thing - we
introduce two more tables here, NOTIFICATION_LOG and NOTIFICATION_SEQUENCE, but
have no .sql files for creation of schema for these. Since we're frowning on
autocreate schema in general, we should add that as well to this.
Could you please add that too? I'm okay with doing that as a separate jira due
to the size of this patch and the fact that this has a lot of thrift generated
code that I don't want to see re-regenerated.
> Enable queuing of HCatalog notification events in metastore DB
> --------------------------------------------------------------
>
> Key: HIVE-9174
> URL: https://issues.apache.org/jira/browse/HIVE-9174
> Project: Hive
> Issue Type: New Feature
> Components: HCatalog, Metastore
> Reporter: Alan Gates
> Assignee: Alan Gates
> Attachments: HIVE-9174.patch
>
>
> HCatalog supports notifying listeners of events such as table creation, etc.
> using the MetaStoreEventListener interface. The only non-test implementation
> of this interface today is NotificationListerner, which currently sends
> notifications via JMS. This requires a JMS service to be set up in the
> cluster.
> This JIRA proposes adding a new DbNotificationListener, that will store
> events directly in the metastore, and allow users to access those events via
> HiveMetastoreClient. This avoids the need for a 3rd tool to install and
> manage when listening for events.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
