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

Kuhu Shukla updated TEZ-3726:
-----------------------------
    Attachment: TEZ-3726.001.patch

Initial patch that removes nodeIdShufflePortMap and conf from the 
DeletionTrackerImpl constructor. It now passes an int which is for the number 
of required threads for cleanup.
It passes the required parameters instead. This patch sits on top of TEZ-3725 
(TEZ-3725.001.patch). Looking for some comments on the approach and I can 
rebase the patch once the related JIRA is in.

> DeletionTracker's reflections instantiation should be simpler and generic.
> --------------------------------------------------------------------------
>
>                 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
>         Attachments: TEZ-3726.001.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)

Reply via email to