You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/10 12:17:18 UTC

[jira] [Commented] (SQOOP-2821) Direct export to Netezza : user/owner confusion

    [ https://issues.apache.org/jira/browse/SQOOP-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140644#comment-15140644 ] 

ASF GitHub Bot commented on SQOOP-2821:
---------------------------------------

GitHub user bonnetb opened a pull request:

    https://github.com/apache/sqoop/pull/12

    SQOOP-2821

    Direct export to Netezza : user/owner confusion

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bonnetb/sqoop SQOOP-2821

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sqoop/pull/12.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #12
    
----
commit c0e82d67251ac3fc79e9b75215374cebd5d3eed2
Author: Benjamin BONNET <be...@m4x.org>
Date:   2016-02-10T11:14:49Z

    SQOOP-2821
    Direct export to Netezza : user/owner confusion

----


> 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)