sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Karoly (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-2995) ackward incompatibility introduced by Custom Tool options
Date Mon, 08 Aug 2016 13:42:20 GMT
David Karoly created SQOOP-2995:

             Summary: ackward incompatibility introduced by Custom Tool options
                 Key: SQOOP-2995
                 URL: https://issues.apache.org/jira/browse/SQOOP-2995
             Project: Sqoop
          Issue Type: Bug
            Reporter: David Karoly

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

View raw message