[
https://issues.apache.org/jira/browse/SQOOP-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422298#comment-15422298
]
Hudson commented on SQOOP-2995:
-------------------------------
FAILURE: Integrated in Jenkins build Sqoop-hadoop20 #1056 (See
[https://builds.apache.org/job/Sqoop-hadoop20/1056/])
SQOOP-2995: backward incompatibility introduced by Custom Tool options
(kathleen:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=3bd2952a9b70724f2c180a4b7450043c5de24552])
* (edit) src/test/org/apache/sqoop/util/TestSqoopJsonUtil.java
* (edit) src/java/org/apache/sqoop/util/SqoopJsonUtil.java
> backward incompatibility introduced by Custom Tool options
> ----------------------------------------------------------
>
> Key: SQOOP-2995
> URL: https://issues.apache.org/jira/browse/SQOOP-2995
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.7
> Reporter: David Karoly
> Assignee: Szabolcs Vasas
> Attachments: SQOOP-2995-2.patch, SQOOP-2995.patch
>
>
> SQOOP-2333 adds support for custom options for User Defined Plugins using
> property customtool.options.jsonmap
> When this is used in combination with sqoop metastore we get backward
> incompatible behavior:
> * if a job is created in a previous sqoop version not containing SQOOP-2333,
> the job definition won't contain customtool.options.jsonmap
> * since SQOOP-2333 introduced this is a mandatory property and we get an
> exception if customtool.options.jsonmap is not present
> * therefore 'job -show' or 'job -exec' will fail for any jobs created in
> previous versions not containing SQOOP-2333
> Sqoop should initialize its internal map object (which is restored from the
> 'customtool.options.jsonmap' metastore property) to an empty map instead of
> null even if the 'customtool.options.jsonmap' property is not present in the
> metastore database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
