You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2017/06/07 08:59:18 UTC
[jira] [Work stopped] (HIVE-16813) Incremental REPL LOAD should
load the events in the same sequence as it is dumped.
[ https://issues.apache.org/jira/browse/HIVE-16813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HIVE-16813 stopped by Sankar Hariappan.
-----------------------------------------------
> Incremental REPL LOAD should load the events in the same sequence as it is dumped.
> ----------------------------------------------------------------------------------
>
> Key: HIVE-16813
> URL: https://issues.apache.org/jira/browse/HIVE-16813
> Project: Hive
> Issue Type: Sub-task
> Components: Hive, repl
> Affects Versions: 2.1.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Labels: DR, replication
> Attachments: HIVE-16813.01.patch
>
>
> Currently, incremental REPL DUMP use $dumpdir/<eventID> to dump the metadata and data files corresponding to the event. The event is dumped in the same sequence in which it was generated.
> Now, REPL LOAD, lists the directories inside $dumpdir using listStatus and sort it using compareTo algorithm of FileStatus class which doesn't check the length before sorting it alphabetically.
> Due to this, the event-100 is processed before event-99 and hence making the replica database non-sync with source.
> Need to use a customized compareTo algorithm to sort the FileStatus.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)