[
https://issues.apache.org/jira/browse/HIVE-15180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682862#comment-15682862
]
Vaibhav Gumashta commented on HIVE-15180:
-----------------------------------------
[~mohitsabharwal] [~ctang.ma] could you also take a look at the patch since it
looks you are also working on the same part of code.
Basically, as part of HIVE-14841 (proposed design:
https://cwiki.apache.org/confluence/display/Hive/HiveReplicationv2Development),
we'd like to be able to read and write the notification messages as part of
tasks (hive-exec). However, we noticed that the Messages/MessageFactory are
part of HCat packages. Making hive-exec depend on hcat doesn't seem like a good
idea. As a result, we've created a copy of the message related code in the
metastore package with the aim of deprecating the HCat classes some time in
future. In this patch, we've also made DBNotificationListener depend on the
classes from the new package instead of the old one. We've also incorporated
the changes you made as part of HIVE-15232 (function/index) events.
Let us know your thoughts on this. If you'd like to discuss any parts of the
proposal, we'll be happy to schedule a call to discuss the ideas and get your
feedback.
> Extend JSONMessageFactory to store additional information about metadata
> objects on different table events
> ----------------------------------------------------------------------------------------------------------
>
> Key: HIVE-15180
> URL: https://issues.apache.org/jira/browse/HIVE-15180
> Project: Hive
> Issue Type: Sub-task
> Components: repl
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Attachments: HIVE-15180.1.patch, HIVE-15180.2.patch,
> HIVE-15180.3.patch, HIVE-15180.3.patch, HIVE-15180.4.patch,
> HIVE-15180.5.patch, HIVE-15180.6.patch, HIVE-15180.6.patch
>
>
> We want the {{NOTIFICATION_LOG}} table to capture additional information
> about the metadata objects when {{DbNotificationListener}} captures different
> events for a table (create/drop/alter) and a partition (create/alter/drop).
> We'll use the messages field to add json objects for table and partitions for
> create and alter events. The drop events message remains unchanged. These
> messages can then be used to replay these events on the destination in event
> of a replication, in a way that will put the destination in a state that's
> consistent with one of the past states of the source.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
