You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Kuhu Shukla (JIRA)" <ji...@apache.org> on 2016/11/18 18:18:58 UTC

[jira] [Updated] (TEZ-3509) Make DAG Deletion Tracker configurable for ContainerLaunchers

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

Kuhu Shukla updated TEZ-3509:
-----------------------------
    Summary: Make DAG Deletion Tracker configurable for ContainerLaunchers  (was: Make DAG Deletion path based)

> Make DAG Deletion Tracker configurable for ContainerLaunchers
> -------------------------------------------------------------
>
>                 Key: TEZ-3509
>                 URL: https://issues.apache.org/jira/browse/TEZ-3509
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>             Fix For: TEZ-3334
>
>         Attachments: TEZ-3509.001.patch, TEZ-3509.002.patch, TEZ-3509.003.patch, TEZ-3509.004.patch, TEZ-3509.005.patch
>
>
> The idea here is to have the API take a path to delete, be it DAG path today or a vertex level path later on. The current implementation takes a flag which is specific to DAG deletion. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)