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

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

                Author: ASF GitHub Bot
            Created on: 29/Apr/21 12:10
            Start Date: 29/Apr/21 12:10
    Worklog Time Spent: 10m 
      Work Description: marton-bod opened a new pull request #2233:
URL: https://github.com/apache/hive/pull/2233


   - Get task num from job conf under a key, instead of hacking the 
numReduceTasks function
   - We can still use numReduceTasks/numMapTasks as a fall back
   - Increasing test timeout due to recent failure with 200 secs


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


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

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

> Get number of write tasks from jobConf for Iceberg commits
> ----------------------------------------------------------
>
>                 Key: HIVE-25076
>                 URL: https://issues.apache.org/jira/browse/HIVE-25076
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Marton Bod
>            Assignee: Marton Bod
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When writing empty data into Iceberg tables, we can end up with 0 succeeded 
> task count number. With the current logic, we might then erroneously end up 
> taking the number of mapper tasks in the commit logic, which would result in 
> failures. We should instead save the number of succeeded task count into the 
> JobConf under a specified key and retrieve it from there.



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

Reply via email to