[
https://issues.apache.org/jira/browse/SQOOP-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087513#comment-13087513
]
Hudson commented on SQOOP-317:
------------------------------
Integrated in Sqoop-jdk-1.6 #13 (See
[https://builds.apache.org/job/Sqoop-jdk-1.6/13/])
SQOOP-317. Allow working with tables owned by other users in Oracle.
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1159491
Files :
* /incubator/sqoop/trunk/src/test/com/cloudera/sqoop/manager/OracleUtils.java
*
/incubator/sqoop/trunk/src/test/com/cloudera/sqoop/manager/OracleManagerTest.java
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/manager/OracleManager.java
> 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
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
