[
https://issues.apache.org/jira/browse/HIVE-16727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021370#comment-16021370
]
ASF GitHub Bot commented on HIVE-16727:
---------------------------------------
GitHub user sankarh opened a pull request:
https://github.com/apache/hive/pull/186
HIVE-16727: REPL DUMP for insert event should't fail if the table is
already dropped.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sankarh/hive HIVE-16727
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/186.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #186
----
commit c06a9df4c2c1a735dc8c0139ebdf6451cc6c9017
Author: Sankar Hariappan <[email protected]>
Date: 2017-05-22T08:15:54Z
HIVE-16727: REPL DUMP for insert event should't fail if the table is
already dropped.
----
> 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
>
> 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)
