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] [Comment Edited] (HIVE-16006) Incremental REPL LOAD doesn't operate on the target database if name differs from source database.
Date Tue, 28 Feb 2017 11:20:45 GMT

    [ https://issues.apache.org/jira/browse/HIVE-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887822#comment-15887822
] 

Sankar Hariappan edited comment on HIVE-16006 at 2/28/17 11:20 AM:
-------------------------------------------------------------------

[~sushanth], I made changes to set isInsert flag while instantiating ReplicationSpec during
event dump and then uses it while import.
Please review the patch-02.


was (Author: sankarh):
[~sushanth] Made changes to set isInsert flag while instantiating ReplicationSpec during event
dump and then uses it while import.
Please review the patch-02.

> Incremental REPL LOAD 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.



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

Mime
View raw message