[
https://issues.apache.org/jira/browse/HIVE-20531?focusedWorklogId=446657&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-446657
]
ASF GitHub Bot logged work on HIVE-20531:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jun/20 16:52
Start Date: 16/Jun/20 16:52
Worklog Time Spent: 10m
Work Description: github-actions[bot] closed pull request #431:
URL: https://github.com/apache/hive/pull/431
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 446657)
Time Spent: 20m (was: 10m)
> Repl load on cloud storage file system can skip redundant move or add
> partition tasks.
> --------------------------------------------------------------------------------------
>
> 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, HIVE-20531.02.patch,
> HIVE-20531.03.patch, HIVE-20531.04.patch, HIVE-20531.05.patch,
> HIVE-20531.06.patch, HIVE-20531.07.patch, HIVE-20531.08.patch,
> HIVE-20531.09.patch, HIVE-20531.10.patch, HIVE-20531.11.patch,
> HIVE-20531.12.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
