You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Syed Shameerur Rahman (Jira)" <ji...@apache.org> on 2021/01/22 09:58:00 UTC

[jira] [Issue Comment Deleted] (HIVE-23737) LLAP: Reuse dagDelete Feature Of Tez Custom Shuffle Handler Instead Of LLAP's dagDelete

     [ https://issues.apache.org/jira/browse/HIVE-23737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Syed Shameerur Rahman updated HIVE-23737:
-----------------------------------------
    Comment: was deleted

(was: [~abstractdog] Could you please review the PR?)

> LLAP: Reuse dagDelete Feature Of Tez Custom Shuffle Handler Instead Of LLAP's dagDelete
> ---------------------------------------------------------------------------------------
>
>                 Key: HIVE-23737
>                 URL: https://issues.apache.org/jira/browse/HIVE-23737
>             Project: Hive
>          Issue Type: Improvement
>          Components: llap
>            Reporter: Syed Shameerur Rahman
>            Assignee: Syed Shameerur Rahman
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> LLAP have a dagDelete feature added as part of HIVE-9911, But now that Tez have added support for dagDelete in custom shuffle handler (TEZ-3362) we could re-use that feature in LLAP. 
> There are some added advantages of using Tez's dagDelete feature rather than the current LLAP's dagDelete feature.
> 1) We can easily extend this feature to accommodate the upcoming features such as vertex and failed task attempt shuffle data clean up. Refer TEZ-3363 and TEZ-4129
> 2) It will be more easier to maintain this feature by separating it out from the Hive's code path. 



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