hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Peña (JIRA) <>
Subject [jira] [Commented] (HIVE-10562) Add versioning/format mechanism to NOTIFICATION_LOG entries, expand MESSAGE size
Date Thu, 16 Feb 2017 16:11:42 GMT


Sergio Peña commented on HIVE-10562:

[~thejas] The job and the server that were running the tests were lost last year when the
private Jenkins server crashed. We're not running those tests, but [~ngangam] has been working
on bringing the job back with other tests that validate data corruption.

> Add versioning/format mechanism to NOTIFICATION_LOG entries, expand MESSAGE size
> --------------------------------------------------------------------------------
>                 Key: HIVE-10562
>                 URL:
>             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,
> 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