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

Posted to dev@oozie.apache.org by "Peter Cseh (JIRA)" <ji...@apache.org> on 2017/05/31 08:58:04 UTC

[jira] [Updated] (OOZIE-2699) OYA: Refactor JavaActionExecutor and executor class hierarchy

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

Peter Cseh updated OOZIE-2699:
------------------------------
    Parent Issue: OOZIE-2889  (was: OOZIE-1770)

> OYA: Refactor JavaActionExecutor and executor class hierarchy
> -------------------------------------------------------------
>
>                 Key: OOZIE-2699
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2699
>             Project: Oozie
>          Issue Type: Sub-task
>            Reporter: Peter Bacsko
>
> Currently JavaActionExecutor has _way_ too much responsibility. A lot of things inside the class are absolutely unrelated to the Java action itself.
> Not only that, the class is too big. A lot of code should be moved to somewhere else, eg. submitting the action to YARN should be handled separately in a different class.
> If implemented properly, old and new classes will be more testable and code coverage will increase.



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