[HIVE-15652] Optimize(reduce) the number of alter calls made to fix repl.last.id

• Type: Sub-task
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Assignee: Sushanth Sowmyan
• Reporter: Sushanth Sowmyan
• Created: 18/Jan/17 00:42
• Updated: 18/Jan/17 11:26

Description

Per code review from HIVE-15534, we might be doing alters to parent objects to set repl.last.id when it is not necessary, since some future event might make this alter redundant.

There are 3 cases where this might happen:

a) After a CREATE_TABLE event - any prior reference to that table does not need an ALTER, since CREATE_TABLE will have a repl.last.id come with it.
b) After a DROP_TABLE event - any prior reference to that table is irrelevant, and thus, no alter is needed.
c) After an ALTER_TABLE event, since that dump will itself do a metadata update that will get the latest repl.last.id along with this event.

In each of these cases, we can remove the alter call needed.

Issue Links

• is related to: HIVE-15534 Update db/table repl.last.id at the end of REPL LOAD of a batch of events
• links to: Reviewboard link