[
https://issues.apache.org/jira/browse/SQOOP-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169513#comment-15169513
]
Abhijeet Apsunde commented on SQOOP-317:
----------------------------------------
Is there some change between versions that might have reversed this fix ? I'm
on 1.4.6 and facing similar issue though Jira says its fixed since
1.4.0-Incubating.
I'm trying to get a table that I dont own, but have READ grants, Following is
snippet of error log:
3488 [uber-SubtaskRunner] INFO org.apache.sqoop.manager.SqlManager -
Executing SQL statement: SELECT t.* FROM res t WHERE 1=0
3791 [uber-SubtaskRunner] ERROR org.apache.sqoop.tool.ImportTool - Imported
Failed: There is no column found in the target table res. Please ensure that
your table name is correct.
When I execute the metadata query fro Oracle SQL Developer it executes
successfully.
> OracleManager should allow working with tables owned by other users.
> --------------------------------------------------------------------
>
> Key: SQOOP-317
> URL: https://issues.apache.org/jira/browse/SQOOP-317
> Project: Sqoop
> Issue Type: Bug
> Reporter: Arvind Prabhakar
> Assignee: Arvind Prabhakar
> Fix For: 1.4.0-incubating
>
> Attachments: SQOOP-317-1.diff, SQOOP-317.diff
>
>
> The default Oracle connector in Sqoop uses user-specific catalog views for
> doing metadata lookup queires. This results in failure when the table is not
> owned by the user that Sqoop connects as.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
