You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/04/15 01:22:16 UTC

[jira] [Commented] (SQOOP-895) Sqoop2: Do not serialize framework and connector configurations into mapreduce configuration object

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

Hudson commented on SQOOP-895:
------------------------------

Integrated in Sqoop2-hadoop200 #265 (See [https://builds.apache.org/job/Sqoop2-hadoop200/265/])
    SQOOP-895: Sqoop2: Do not serialize framework and connector configurations into mapreduce configuration object (Revision 0a0a65a29fcd01251e74e63e8963f8c250e12668)

     Result = SUCCESS
kathleen : https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=0a0a65a29fcd01251e74e63e8963f8c250e12668
Files : 
* execution/mapreduce/src/main/java/org/apache/sqoop/job/mr/ConfigurationUtils.java
* execution/mapreduce/src/main/java/org/apache/sqoop/job/JobConstants.java
* submission/mapreduce/src/main/java/org/apache/sqoop/submission/mapreduce/MapreduceSubmissionEngine.java

                
> Sqoop2: Do not serialize framework and connector configurations into mapreduce configuration object
> ---------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-895
>                 URL: https://issues.apache.org/jira/browse/SQOOP-895
>             Project: Sqoop
>          Issue Type: New Feature
>    Affects Versions: 1.99.1
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.2
>
>         Attachments: bugSQOOP-895.patch
>
>
> One of original Sqoop2 promises was to not save credentials to mapreduce job so that they won't be openly available. I believe that we should keep this promise.

--
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