[SQOOP-2495] Sqoop2: Provide simple test that can validate if connector is reasonably formed

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.99.6
• Fix Version/s: 1.99.8
• Assignee: Jarek Jarcec Cecho
• Reporter: Jarek Jarcec Cecho
• Created: 15/Aug/15 15:34
• Updated: 28/Jul/16 00:27

Description

On internal hackathon we we're hacking Sqoop 2 connector with singhashish and we went through few troubles that we should address.

We have a lot of requirements for Sqoop connectors that are only documented but not enforced by the code, for example:

• Resource bundles need to have names for all properties in configuration objects
• Configuration objects needs to be properly annotated

If either of those is incorrect then we happily load the connector just to throw some random exceptions during runtime. We should provide simple test case that all connectors can reuse to validate that connector is properly formed as Sqoop expects.

(Which still doesn't mean that the connector will work as we can't guarantee that extractor/loader is properly implemented. But we can at least help people to not see random exceptions such as those described in SQOOP-2494).

Issue Links

• depends upon: SQOOP-2877 Sqoop2: Enrich Kite Connector resource file
• depends upon: SQOOP-2881 Sqoop2: EnrichOraOop Connector resource file
• depends upon: SQOOP-2882 Sqoop2: Enrich SFTP Connector resource file
• depends upon: SQOOP-2883 Sqoop2: Update model classes to represent new constant for connector resource bundles
• links to: Review board