Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-1486

Oracle direct connector should use Sqoop merge syntax

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.4.5
    • Fix Version/s: None
    • Component/s: connectors/oracle
    • Labels:
      None

      Description

      From Gwen Shapira

      when running the following sqoop command with OraOop installed:

      sqoop export --table mytable --update-key COL1, COL2, COL3 --export-dir /user/hive/warehouse/mytable --connect "jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 1.1.1.1)(PORT = 1521)))(SDU = 5844)(CONNECT_DATA = (ORACLE_SID = oracle)))" --username scott --password tiger

      The job runs succesfully and reports:
      INFO mapreduce.ExportJobBase: Exported 54 records.

      However not rows actually appears in the table. It appears that Oraoop loads the data into staging tables, but not into the user table.

      When using the Oraoop specific syntax, the export succeeds and we see data in the user table:

      sqoop export -Doraoop.export.merge=true -Doraoop.update.key.extra.columns="COL2" --table mytable --export-dir /user/hive/warehouse/mytable --connect "jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 1.1.1.1)(PORT = 1521)))(SDU = 5844)(CONNECT_DATA = (ORACLE_SID = oracle)))" --username scott --password tiger --input-fields-terminated-by ',' --update-key COL1

      Expected behavior:
      Either make sure the usual Sqoop syntax works with Oraoop, or issue a suitable error message

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              david.robson David Robson
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: