[
https://issues.apache.org/jira/browse/SQOOP-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655766#comment-13655766
]
Hudson commented on SQOOP-1042:
-------------------------------
Integrated in Sqoop2-hadoop100 #280 (See
[https://builds.apache.org/job/Sqoop2-hadoop100/280/])
SQOOP-1042: Sqoop2: Name constraints in Derby repository (Revision
67f6340344c833eae8f565347f60f37b1ac95c6d)
Result = FAILURE
kathleen :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=67f6340344c833eae8f565347f60f37b1ac95c6d
Files :
*
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbySchemaConstants.java
*
repository/repository-derby/src/main/java/org/apache/sqoop/repository/derby/DerbySchemaQuery.java
> Sqoop2: Name constraints in Derby repository
> --------------------------------------------
>
> Key: SQOOP-1042
> URL: https://issues.apache.org/jira/browse/SQOOP-1042
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 1.99.2
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.3
>
> Attachments: bugSQOOP-1042.patch
>
>
> When dealing with foreign key constraints, derby will print similar
> exceptions:
> {code}
> 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
> {code}
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
