Sqoop
  1. Sqoop
  2. SQOOP-1042

Sqoop2: Name constraints in Derby repository

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.99.2
    • Fix Version/s: 1.99.3
    • Component/s: None
    • Labels:
      None

      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.

      1. bugSQOOP-1042.patch
        13 kB
        Jarek Jarcec Cecho

        Issue Links

          Activity

          Jarek Jarcec Cecho created issue -
          Jarek Jarcec Cecho made changes -
          Field Original Value New Value
          Remote Link This issue links to "Review board (Web Link)" [ 12207 ]
          Jarek Jarcec Cecho made changes -
          Attachment bugSQOOP-1042.patch [ 12582809 ]
          Jarek Jarcec Cecho made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Kathleen Ting made changes -
          Status Patch Available [ 10002 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Jarek Jarcec Cecho
              Reporter:
              Jarek Jarcec Cecho
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development