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-16727) REPL DUMP for insert event should't fail if the table is already dropped.
Date Fri, 26 May 2017 09:44:04 GMT

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

Sankar Hariappan updated HIVE-16727:
------------------------------------
    Status: Patch Available  (was: Open)

> REPL DUMP for insert event should't fail if the table is already dropped.
> -------------------------------------------------------------------------
>
>                 Key: HIVE-16727
>                 URL: https://issues.apache.org/jira/browse/HIVE-16727
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Hive, repl
>    Affects Versions: 2.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DR, replication
>         Attachments: HIVE-16727.01.patch, HIVE-16727.02.patch
>
>
> Currently, insert event doesn't log the table object as part of event notification message.
During dump, the table object is obtained from metastore which can be null if the table is
already dropped and hence REPL DUMP fails.
> Steps:
> 1. Bootstrap dump/load with a table.
> 2. Insert into the table.
> 3. Drop the table.
> 4. REPL DUMP (incremental).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message