[
https://issues.apache.org/jira/browse/SQOOP-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481128#comment-13481128
]
Hudson commented on SQOOP-636:
------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop100 #233 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop100/233/])
SQOOP-636: ExportJobTestCase.runExport method does not reuse the existing
Configuration and SqoopOptions (Revision
695666acdbef7b979d2cd64dd96d1808d7241fc0)
Result = SUCCESS
jarcec :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=695666acdbef7b979d2cd64dd96d1808d7241fc0
Files :
* src/test/com/cloudera/sqoop/testutil/ExportJobTestCase.java
> 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
