[ 
https://issues.apache.org/jira/browse/HIVE-15180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Gumashta updated HIVE-15180:
------------------------------------
    Description: 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.  (was: 
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).)

> 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)

Reply via email to