sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Weeks (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-3341) Oracle Data Connector Doesn't Support Case Sensitive Table Names
Date Thu, 12 Jul 2018 21:58:00 GMT
Shawn Weeks created SQOOP-3341:

             Summary: Oracle Data Connector Doesn't Support Case Sensitive Table Names
                 Key: SQOOP-3341
                 URL: https://issues.apache.org/jira/browse/SQOOP-3341
             Project: Sqoop
          Issue Type: Bug
          Components: connectors/oracle
    Affects Versions: 1.4.6
            Reporter: Shawn Weeks

Currently the Oracle Data Connector uppercases table names before querying the data dictionary
for columns causing it to fail when you try to import a lowercase table name. This is probably
caused by OraOopUtilities upper casing the table names under decodeOracleTableName. Ideally
we would just accept the case inputed or try to detect the double quotes around the table
name. From the debug logs you end up with something like this. The message implies some sort
of double quoting will fix the issue but I haven't discovered any combination that does.

The Oracle table context has been derived from:
oracleConnectionUserName = someuser
tableStr = STAGE.blah_201612160955
owner : STAGE
table : BLAH_201612160955

Data Connector for Oracle and Hadoop will not process this Sqoop connection, as the Oracle
user STAGE does not own a table named BLAH_201612160955.
Please prefix the table name with the owner.
Note: You may need to double-quote the owner and/or table name.
E.g. sqoop ... --username someuser --table STAGE.BLAH_201612160955{code}

This message was sent by Atlassian JIRA

View raw message