[jira] [Work logged] (HIVE-25208) Refactor Iceberg commit to the MoveTask/MoveWork

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-25208?focusedWorklogId=607845&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-607845 ]

ASF GitHub Bot logged work on HIVE-25208:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Jun/21 13:04
            Start Date: 07/Jun/21 13:04
    Worklog Time Spent: 10m 
      Work Description: pvary opened a new pull request #2359:
URL: https://github.com/apache/hive/pull/2359


   ### What changes were proposed in this pull request?
   We should use the MoveTask to commit the changes (inserts/insert overwrites)
   
   ### Why are the changes needed?
   MoveTask is used for multiple things, like stat generation. When we removed the Move tasks, we caused several unseen issues. We should reintroduce the MoveTask
   
   ### Does this PR introduce _any_ user-facing change?
   No
   
   ### How was this patch tested?
   Unit tests


-- 
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:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 607845)
    Remaining Estimate: 0h
            Time Spent: 10m

> Refactor Iceberg commit to the MoveTask/MoveWork
> ------------------------------------------------
>
>                 Key: HIVE-25208
>                 URL: https://issues.apache.org/jira/browse/HIVE-25208
>             Project: Hive
>          Issue Type: Improvement
>          Components: Hive
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Instead of committing Iceberg changes in `DefaultMetaHook.preCommitInsert` we should commit in MoveWork so we are using the same flow as normal tables.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)