[SQOOP-1042] Sqoop2: Name constraints in Derby repository

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.99.2
• Fix Version/s: 1.99.3
• Assignee: Jarek Jarcec Cecho
• Reporter: Jarek Jarcec Cecho
• Created: 12/May/13 01:34
• Updated: 13/May/13 05:17
• Resolved: 13/May/13 04:16

Description

When dealing with foreign key constraints, derby will print similar exceptions:

Exception: java.sql.SQLIntegrityConstraintViolationException Message: INSERT on table 'SQ_JOB_INPUT' caused a violation of foreign key constraint 'SQL130511152808250' for key (20).  The statement has been rolled back

Constraint name SQL130511152808250 is auto generated because we are not explicitly naming them in the create script. For simpler debugging, I would suggest to explicitly name all constraints.

Issue Links

• links to: Review board