hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sankar Hariappan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-16785) Ensure replication actions are idempotent if any series of events are applied again.
Date Thu, 15 Jun 2017 14:18:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-16785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sankar Hariappan updated HIVE-16785:
------------------------------------
    Attachment: HIVE-16785.02.patch

Added 02.patch with below updates.
- Added idempotent behaviour for CREATE FUNCTION and DROP FUNCTION operations.

> Ensure replication actions are idempotent if any series of events are applied again.
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-16785
>                 URL: https://issues.apache.org/jira/browse/HIVE-16785
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Hive, repl
>    Affects Versions: 2.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DR, replication
>             Fix For: 3.0.0
>
>         Attachments: HIVE-16785.01.patch, HIVE-16785.02.patch
>
>
> Some of the events(ALTER, RENAME, TRUNCATE) are not idempotent and hence leads to failure
of REPL LOAD if applied twice or applied on an object which is latest than current event.
For example, if TRUNCATE is applied on a table which is already dropped will fail instead
of noop.
> Also, need to consider the scenario where the object is missing while applying an event.
For example, if RENAME_TABLE event is applied on target where the old table is missing should
validate if table should be recreated or should treat the event as noop. This can be done
by verifying the DB level last repl ID against the current event ID.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message