You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/09/11 15:45:00 UTC
[jira] [Commented] (HIVE-20531) One of the task , either move or
add partition can be avoided in repl load flow
[ https://issues.apache.org/jira/browse/HIVE-20531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610816#comment-16610816 ]
ASF GitHub Bot commented on HIVE-20531:
---------------------------------------
GitHub user maheshk114 opened a pull request:
https://github.com/apache/hive/pull/431
HIVE-20531 : One of the task , either move or add partition can be avoided in repl load flow
…
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/maheshk114/hive HIVE-20531
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/431.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 #431
----
commit a7c693696bd961937db3a3594c4717b4f180e48e
Author: Mahesh Kumar Behera <mb...@...>
Date: 2018-09-11T11:25:26Z
HIVE-20531 : One of the task , either move or add partition can be avoided in repl load flow
----
> One of the task , either move or add partition can be avoided in repl load flow
> -------------------------------------------------------------------------------
>
> Key: HIVE-20531
> URL: https://issues.apache.org/jira/browse/HIVE-20531
> Project: Hive
> Issue Type: Sub-task
> Components: repl
> Affects Versions: 4.0.0
> Reporter: mahesh kumar behera
> Assignee: mahesh kumar behera
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-20531.01.patch
>
>
> In replication load, both add partition and insert operations are handled through import. Import creates 3 major tasks. Copy, add partition and move. Copy does the copy of data from source location to staging directory. Then add partition (which runs in parallel to copy) creates the partition in meta store. Its a no op in case of insert and by the time this ddl task is executed for insert partition would be already present. The third operation is move. Which actually moves the file from staging directory to actual location. And then in case of insert it adds the insert event to notification table. It does this for add partition operation which is redundant as the event for add partition would have been written already by ddl task. With the optimization to copy directly to actual table location in S3, move task can be avoided for add partition operation replay and replay of insert need not create the add partition (ddl) task.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)