hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-16727) REPL DUMP for insert event should't fail if the table is already dropped.
Date Tue, 30 May 2017 06:38:04 GMT

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

Thejas M Nair updated HIVE-16727:
---------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

Patch committed to master. Thanks Sankar!


> 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
>             Fix For: 3.0.0
>
>         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