[SQOOP-2995] backward incompatibility introduced by Custom Tool options

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.7
• Fix Version/s: 1.4.7
• Assignee: Vasas Szabolcs
• Reporter: David Karoly
• Created: 08/Aug/16 13:42
• Updated: 16/Jun/17 04:31
• Resolved: 16/Aug/16 05:56

Description

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.

Issue Links

• is broken by: SQOOP-2333 Sqoop to support Custom options for User Defined Plugins(Tool)
• links to: ReviewBoard