sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1017) Sqoop2: Split FrameworkManager into two classes
Date Thu, 20 Jun 2013 23:23:21 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689835#comment-13689835
] 

Jarek Jarcec Cecho commented on SQOOP-1017:
-------------------------------------------

The failure in profile 100 is jenkins memory issue.
                
> 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
>             Fix For: 1.99.3
>
>         Attachments: SQOOP-1017.patch
>
>
> 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

Mime
View raw message