sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3206) Make sqoop fail if user uses --direct connector and tries to encode a null value when using a MySQL database
Date Thu, 06 Jul 2017 09:22:00 GMT

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

ASF subversion and git services commented on SQOOP-3206:
--------------------------------------------------------

Commit 2c199a7f4fc744f653f036d5afb6f49b0d4c445c in sqoop's branch refs/heads/trunk from [~anna.szonyi]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=2c199a7 ]

SQOOP-3206: Make sqoop fail if user uses --direct connector and tries to encode a null value
when using a MySQL database

(Zach Berkowitz via Anna Szonyi)


> Make sqoop fail if user uses --direct connector and tries to encode a null value when
using a MySQL database
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-3206
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3206
>             Project: Sqoop
>          Issue Type: Improvement
>            Reporter: Zach Berkowitz
>            Assignee: Zach Berkowitz
>            Priority: Minor
>         Attachments: sqoop-3206.patch
>
>
> The MySQL tools, mysqldump and mysqlimport, do not support custom null value options,
so sqoop should fail fast when --direct mode and --input-null-string, --input-null-non-string,
--null-string, or --null-non-string are used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message