hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-21197) Hive replication can add duplicate data during migration to a target with hive.strict.managed.tables enabled
Date Sun, 24 Feb 2019 14:22:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-21197?focusedWorklogId=203246&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-203246
]

ASF GitHub Bot logged work on HIVE-21197:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Feb/19 14:21
            Start Date: 24/Feb/19 14:21
    Worklog Time Spent: 10m 
      Work Description: maheshk114 commented on pull request #541: HIVE-21197 : Hive Replication
can add duplicate data during migration to a target with hive.strict.managed.tables enabled
URL: https://github.com/apache/hive/pull/541#discussion_r259622991
 
 

 ##########
 File path: ql/src/java/org/apache/hadoop/hive/ql/txn/compactor/Initiator.java
 ##########
 @@ -112,6 +118,12 @@ public void run() {
                 continue;
               }
 
+              if (replIsCompactionDisabledForTable(t)) {
 
 Review comment:
   not done
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 203246)
    Time Spent: 11h 10m  (was: 11h)

> Hive replication can add duplicate data during migration to a target with hive.strict.managed.tables
enabled
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-21197
>                 URL: https://issues.apache.org/jira/browse/HIVE-21197
>             Project: Hive
>          Issue Type: Task
>          Components: repl
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-21197.01.patch, HIVE-21197.02.patch
>
>          Time Spent: 11h 10m
>  Remaining Estimate: 0h
>
> During bootstrap phase it may happen that the files copied to target are created by events
which are not part of the bootstrap. This is because of the fact that, bootstrap first gets
the last event id and then the file list. During this period if some event are added, then
bootstrap will include files created by these events also.The same files will be copied again
during the first incremental replication just after the bootstrap. In normal scenario, the
duplicate copy does not cause any issue as hive allows the use of target database only after
the first incremental. But in case of migration, the file at source and target are copied
to different location (based on the write id at target) and thus this may lead to duplicate
data at target. This can be avoided by having at check at load time for duplicate file. This
check can be done only for the first incremental and the search can be done in the bootstrap
directory (with write id 1). if the file is already present then just ignore the copy.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message