You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2017/06/02 12:03:04 UTC

[jira] [Created] (HIVE-16813) Incremental REPL LOAD should load the events in the same sequence as it is dumped.

Sankar Hariappan created HIVE-16813:
---------------------------------------

             Summary: 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


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 unreliable.

Need to use a customised compareTo algorithm to sort the FileStatus.



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