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

Posted to dev@sqoop.apache.org by "Zach Berkowitz (JIRA)" <ji...@apache.org> on 2017/08/17 12:46:00 UTC

[jira] [Updated] (SQOOP-3206) Make sqoop fail if user uses --direct connector and tries to encode a null value when using a MySQL database

     [ https://issues.apache.org/jira/browse/SQOOP-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zach Berkowitz updated SQOOP-3206:
----------------------------------
    Attachment: SQOOP-3216-2.patch

Updated Patch 

> 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, SQOOP-3216-2.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)