You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2013/01/11 09:00:18 UTC
[jira] [Commented] (SQOOP-828) Document import failure common cause
in Sqoop Troubleshooting Guide
[ https://issues.apache.org/jira/browse/SQOOP-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550951#comment-13550951 ]
Jarek Jarcec Cecho commented on SQOOP-828:
------------------------------------------
I'm not sure that this usage is generic to Sqoop framework, but I do know that some of the connectors are using it (for example Oracle connector). I would therefore suggest to put this into Oracle specific part of Troubleshooting guide (and other connectors that are using this if any).
Jarcec
> Document import failure common cause in Sqoop Troubleshooting Guide
> -------------------------------------------------------------------
>
> Key: SQOOP-828
> URL: https://issues.apache.org/jira/browse/SQOOP-828
> Project: Sqoop
> Issue Type: Bug
> Components: connectors, docs
> Affects Versions: 1.4.2
> Reporter: Kathleen Ting
>
> We should document this error in the Sqoop Troubleshooting Guide.
> ERROR tool.ImportTool: Imported Failed: Attempted to generate class with no columns!
> We've verified that the table is being owned by a different user than is used to access the data. In such case, the user needs to specify the table owner in the table parameter separated by dot, for example:
> --table owner.tableName
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira