You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "jiraposter@reviews.apache.org (JIRA)" <ji...@apache.org> on 2011/09/23 05:19:28 UTC
[jira] [Commented] (SQOOP-351) Sqoop User Guide's troubleshooting
section should include Case-Sensitive Catalog Query Errors
[ https://issues.apache.org/jira/browse/SQOOP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113128#comment-13113128 ]
jiraposter@reviews.apache.org commented on SQOOP-351:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2031/
-----------------------------------------------------------
Review request for Sqoop and Arvind Prabhakar.
Summary
-------
Updated documentation.
This addresses bug SQOOP-351.
https://issues.apache.org/jira/browse/SQOOP-351
Diffs
-----
src/docs/user/troubleshooting.txt b2eb5ee
Diff: https://reviews.apache.org/r/2031/diff
Testing
-------
Built docs and verified.
Thanks,
Kate
> Sqoop User Guide's troubleshooting section should include Case-Sensitive Catalog Query Errors
> ---------------------------------------------------------------------------------------------
>
> Key: SQOOP-351
> URL: https://issues.apache.org/jira/browse/SQOOP-351
> Project: Sqoop
> Issue Type: Improvement
> Components: docs
> Reporter: Kate Ting
> Assignee: Kate Ting
>
> While working with Oracle, a common problem is that Sqoop can not figure out column names. This happens because the catalog queries that Sqoop uses for Oracle expect the correct case to be specified for the user name and table name. It would be helpful if this was documented in the troubleshooting section of the Sqoop User Guide.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira