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] [Commented] (HIVE-16813) Incremental REPL LOAD should load the events in the same sequence as it is dumped.
Date Mon, 05 Jun 2017 17:57:04 GMT

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

ASF GitHub Bot commented on HIVE-16813:
---------------------------------------

GitHub user sankarh opened a pull request:

    https://github.com/apache/hive/pull/192

    HIVE-16813: Incremental REPL LOAD should load the events in the same sequence as it is
dumped.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sankarh/hive HIVE-16813

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hive/pull/192.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #192
    
----
commit ba709ab7101cad69d5f6fc82bf031fea217e669e
Author: Sankar Hariappan <mailtosankarh@gmail.com>
Date:   2017-06-05T17:53:34Z

    HIVE-16813: Incremental REPL LOAD should load the events in the same sequence as it is
dumped.

----


> 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
>
> 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)

Mime
View raw message