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-636) ExportJobTestCase.runExport method does not reuse the existing Configuration and SqoopOptions
Date Mon, 22 Oct 2012 01:24:12 GMT

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

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

It's pretty small patch, so I'm giving my +1 here.
                
> ExportJobTestCase.runExport method does not reuse the existing Configuration and SqoopOptions

> ----------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-636
>                 URL: https://issues.apache.org/jira/browse/SQOOP-636
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.2
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>            Priority: Trivial
>              Labels: test
>             Fix For: 1.4.3
>
>         Attachments: SQOOP-636.patch
>
>
> The utility method runExport creates Sqoop object with out Configuration and SqoopOptions
which has the side effect of ignoring what is overridden by the implementing class and creates
new ones. ImportJobTestCase does the right thing.

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