tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kuhu Shukla (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TEZ-3726) Clean up DeletionTracker's reflection instantiation and provide ContainerLauncher with dagComplete() functionality
Date Wed, 17 May 2017 15:36:04 GMT

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

Kuhu Shukla resolved TEZ-3726.
------------------------------
       Resolution: Fixed
    Fix Version/s: TEZ-3334

Committed to TEZ-3334 feature branch.

> Clean up DeletionTracker's reflection instantiation and provide ContainerLauncher with
dagComplete() functionality
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: TEZ-3726
>                 URL: https://issues.apache.org/jira/browse/TEZ-3726
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>             Fix For: TEZ-3334
>
>         Attachments: TEZ-3726.001.patch, TEZ-3726.002.patch, TEZ-3726.003.patch, TEZ-3726.004.patch
>
>
> This JIRA will address the following feedback from [~jlowe].
> {code}
> The reflection instantiation is invoking a constructor signature that isn't in the DeletionTracker
abstract class? Isn't that too much knowledge about the actual class being created?
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message