You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2017/05/15 14:41:04 UTC
[jira] [Commented] (TEZ-3726) DeletionTracker's reflections
instantiation should be simpler and generic.
[ https://issues.apache.org/jira/browse/TEZ-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010624#comment-16010624 ]
Jason Lowe commented on TEZ-3726:
---------------------------------
The patch doesn't apply to the TEZ-3334 branch.
> 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, TEZ-3726.002.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)