hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sankar Hariappan (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HIVE-16813) Incremental REPL LOAD should load the events in the same sequence as it is dumped.
Date Fri, 02 Jun 2017 12:03:04 GMT
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)

Mime
View raw message