[
https://issues.apache.org/jira/browse/SQOOP-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512050#comment-13512050
]
Venkat Ranganathan commented on SQOOP-741:
------------------------------------------
Thanks Jarek for committing this
> The OracleConnect getTables() implementation needs to restrict tables to
> current user
> -------------------------------------------------------------------------------------
>
> Key: SQOOP-741
> URL: https://issues.apache.org/jira/browse/SQOOP-741
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.2
> Environment: Oracle 11g
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Fix For: 1.4.3
>
> Attachments: SQOOP-741.patch
>
>
> SQOOP has various managers specific to each Database. Each of these
> managers provide database specific queries to list databases, tables, table
> columns, etc. The Oracle implementation
> (org.apache.sqoop.manager.OracleManager) defines queries specific for Oracle.
> The query for list tables in this implementation provides a list of all the
> tables the user has access to.
> This is inconsistent with the other queries defined (for getting list of
> table columns, get primary key for table etc) which restrict the table being
> queried to be owned by the user.
> This inconsisent behavior has more issues. For example, when we do
> import-all-tables (subject to other restrictions of import-all-tables), it
> fails because the list tables query used by import all tables returns tables
> like DUAL (which is a dummy Oracle table that gets blessed into all user
> schemas for historical reasons and other tables).
> I can provide a patch for this if there is agreement that this behavior needs
> fixing (and it will make Oracle manager work like other database connectors
> at least in spirit)
--
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
