[
https://issues.apache.org/jira/browse/HIVE-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869171#comment-15869171
]
Thejas M Nair commented on HIVE-10562:
--------------------------------------
[~spena]
For some reason the tests for metastore schema upgrade in HIVE-9800 didn't get
kicked off in this case. Any idea why ?
> Add versioning/format mechanism to NOTIFICATION_LOG entries, expand MESSAGE
> size
> --------------------------------------------------------------------------------
>
> Key: HIVE-10562
> URL: https://issues.apache.org/jira/browse/HIVE-10562
> Project: Hive
> Issue Type: Sub-task
> Components: Import/Export
> Affects Versions: 1.2.0
> Reporter: Sushanth Sowmyan
> Assignee: Sushanth Sowmyan
> Fix For: 2.2.0
>
> Attachments: HIVE-10562.2.patch, HIVE-10562.3.patch,
> HIVE-10562.4.patch, HIVE-10562.5.patch, HIVE-10562.patch
>
>
> 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
(v6.3.15#6346)
