Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
This JIRA will address the following review comment from jlowe.
Does it make sense to create an abstract class in tez-common that derives from ContainerLauncher and has an abstract dagComplete method? Then we can have the existing launchers derive from that rather than ContainerLauncher directly and can RTTI check against that one class rather than maintain a specific list of container launchers.
Attachments
Attachments
Issue Links
- duplicates
-
TEZ-3726 Clean up DeletionTracker's reflection instantiation and provide ContainerLauncher with dagComplete() functionality
- Closed