[HIVE-10562] Add versioning/format mechanism to NOTIFICATION_LOG entries, expand MESSAGE size

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 2.2.0
• Component/s: Import/Export
• Assignee: Sushanth Sowmyan Assign to me
• Reporter: Sushanth Sowmyan
• Created: 30/Apr/15 22:23
• Updated: 26/Jul/17 03:30
• Resolved: 13/Feb/17 04:41

Description

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.

Issue Links

• is related to: HIVE-15930 Syntax error in the MySQL metastore schema definition
• is related to: HIVE-16577 Syntax error in the metastore init scripts for mssql