[
https://issues.apache.org/jira/browse/SQOOP-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086700#comment-13086700
]
[email protected] commented on SQOOP-317:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1579/
-----------------------------------------------------------
Review request for Sqoop, jmhsieh and Bilung Lee.
Summary
-------
Modified OracleManager implementation to use global catalog views instead of
user-specific views for metadata queries. Also introduced a test case that
specifically exercises the functionality in question. Note that if this gets
committed, the Oracle test configuration would need to be changed in order to
introduce a new user that will be used by the OracleManagerTest.
This addresses bug SQOOP-317.
https://issues.apache.org/jira/browse/SQOOP-317
Diffs
-----
/src/java/com/cloudera/sqoop/manager/OracleManager.java 1158963
/src/test/com/cloudera/sqoop/manager/OracleManagerTest.java 1158963
/src/test/com/cloudera/sqoop/manager/OracleUtils.java 1158963
Diff: https://reviews.apache.org/r/1579/diff
Testing
-------
All unit and thirdparty tests along with some manual testing.
Thanks,
Arvind
> 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
