hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <>
Subject [jira] [Commented] (HIVE-10562) Add version column to NOTIFICATION_LOG table and DbNotificationListener
Date Fri, 06 Jan 2017 00:31:58 GMT


Sushanth Sowmyan commented on HIVE-10562:

Note - moving this to the replv2 umbrella. In addition to version, we should ideally allow
some notion of what "format" was used to encode the message - i.e. which MessageFactory was
used. Currently, we figure out which MessageFactory to instantiate from conf, but that isn't
durable over time in case we're reading messages created by an older MessageFactory.

> Add version column to NOTIFICATION_LOG table and DbNotificationListener
> -----------------------------------------------------------------------
>                 Key: HIVE-10562
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Import/Export
>    Affects Versions: 1.2.0
>            Reporter: Sushanth Sowmyan
> Currently, we have a JSON encoded message being stored in the NOTIFICATION_LOG table.
> If we want to be future proof, we need to allow for versioning of this message, since
we might change what gets stored in the message. A prime example of what we'd want to change
is as in HIVE-10393.
> MessageFactory already has stubs to allow for versioning of messages, and we could expand
on this further in the future. NotificationListener currently encodes the message version
into the header for the JMS message it sends, which seems to be the right place for a message
version (instead of being contained in the message, for eg.).
> So, we should have a similar ability for DbEventListener as well, and the place this
makes the most sense is to and add a version column to the NOTIFICATION_LOG table.

This message was sent by Atlassian JIRA

View raw message