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

Posted to dev@sqoop.apache.org by "Venkat Ranganathan (JIRA)" <ji...@apache.org> on 2013/04/26 22:28:15 UTC

[jira] [Assigned] (SQOOP-1017) Sqoop2: Split FrameworkManager into two classes

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

Venkat Ranganathan reassigned SQOOP-1017:
-----------------------------------------

    Assignee: Venkat Ranganathan
    
> Sqoop2: Split FrameworkManager into two classes
> -----------------------------------------------
>
>                 Key: SQOOP-1017
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1017
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.99.2
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Venkat Ranganathan
>
> Current {{FrameworkManager}} implementation is serving several purposes - it holds framework metadata and drives job execution. I believe that we should separate that into different classes for simpler future maintenance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira