[
https://issues.apache.org/jira/browse/HIVE-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889479#comment-15889479
]
Sushanth Sowmyan commented on HIVE-16006:
-----------------------------------------
Code-wise, this version fixes the issue correctly, and is the kind of change to
ReplicationSpec that I thought was necessary. :)
However, from the test that was added, I see that that test succeeds even
without these changes. i.e., if I pick only the test change and nothing else,
the test still succeeds, which it should not, since this patch is what fixes
the bug. Could you look into the test to see why that is?
> Incremental REPL LOAD Inserts doesn't operate on the target database if name
> differs from source database.
> ----------------------------------------------------------------------------------------------------------
>
> Key: HIVE-16006
> URL: https://issues.apache.org/jira/browse/HIVE-16006
> Project: Hive
> Issue Type: Sub-task
> Components: repl
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Attachments: HIVE-16006.01.patch, HIVE-16006.02.patch
>
>
> During "Incremental Load", it is not considering the database name input in
> the command line. Hence load doesn't happen. At the same time, database with
> original name is getting modified.
> Steps:
> 1. REPL DUMP default FROM 52;
> 2. REPL LOAD replDb FROM '/tmp/dump/1487588522621';
> – This step modifies the default Db instead of replDb.
> ==
> Additional note - this is happening for INSERT events, not other events.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
