[
https://issues.apache.org/jira/browse/SQOOP-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin BONNET updated SQOOP-2821:
-----------------------------------
Description:
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
was:
Hi,
when exporting to Netezza, if connected user (in the Netezza URL) is not the
target table owner, things go wrong :
- if you don 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
> 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
>
> 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)
