[
https://issues.apache.org/jira/browse/HIVE-15652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sushanth Sowmyan updated HIVE-15652:
------------------------------------
Attachment: HIVE-15652.patch
Patch attached, this changes the total number of Alters to update repl.last.id
across TestReplicationScenarios from 60 to 44.
> Optimize(reduce) the number of alter calls made to fix repl.last.id
> -------------------------------------------------------------------
>
> Key: HIVE-15652
> URL: https://issues.apache.org/jira/browse/HIVE-15652
> Project: Hive
> Issue Type: Bug
> Reporter: Sushanth Sowmyan
> Assignee: Sushanth Sowmyan
> Attachments: HIVE-15652.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
