[
https://issues.apache.org/jira/browse/SQOOP-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140667#comment-15140667
]
Benjamin BONNET commented on SQOOP-2821:
----------------------------------------
Hi,
This is how it works :
1) direct netezza manager checks if table exists, using table name if it is
qualified (=> owner.table), or table name + connected user name (assuming
user=owner) if table name is not qualified
2) sqlmanager uses table name to get column names. But using a qualified name,
sqlmanager will fail to get column names (since it will request for a twice
qualified table : owner.owner.table)
That patch just unqualifies table name so that sqlmanager can use it.
Regards
> Direct export to Netezza : user/owner confusion
> -----------------------------------------------
>
> Key: SQOOP-2821
> URL: https://issues.apache.org/jira/browse/SQOOP-2821
> Project: Sqoop
> Issue Type: Bug
> Components: connectors
> Affects Versions: 1.4.6
> Reporter: Benjamin BONNET
> Attachments: SQOOP-2821.patch
>
>
> Hi,
> when exporting to Netezza, if connected user (in the Netezza URL) is not the
> target table owner, things go wrong :
> - if you do not use qualified table name, the table existence check will fail
> since SQOOP will assume table owner is the same as connected user
> - if you do use qualified table name, the table existence check will succeed
> but table export will fail since SQOOP will try to export to a twice
> qualified table (db.owner.owner.table instead of db.owner.table)
> Regards
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
