[
https://issues.apache.org/jira/browse/SQOOP-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545685#comment-16545685
]
Shawn Weeks commented on SQOOP-3341:
------------------------------------
So it turns out the syntax is just really weird and undocumented. For example
this keeps the quotes but it seems like it would be a lot more obvious if we
just used the case that was passed into Sqoop instead like with do for
map-column-hive.
{code:java}
--table '""SWDBA"'.'"ThisIsATestTable""'{code}
> 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
> Priority: Minor
>
> 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.
>
> {code:java}
> The Oracle table context has been derived from:
> oracleConnectionUserName = someuser
> tableStr = STAGE.blah_201612160955
> as:
> 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
(v7.6.3#76005)
