sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-484) Update troubleshooting guide section about MySQL and TINYINT(1) columns
Date Sat, 12 May 2012 14:08:49 GMT

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

Jarek Jarcec Cecho updated SQOOP-484:
-------------------------------------

    Attachment: SQOOP-484.patch
    
> Update troubleshooting guide section about MySQL and TINYINT(1) columns
> -----------------------------------------------------------------------
>
>                 Key: SQOOP-484
>                 URL: https://issues.apache.org/jira/browse/SQOOP-484
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: docs
>    Affects Versions: 1.4.1-incubating
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>            Priority: Trivial
>             Fix For: 1.4.2-incubating
>
>         Attachments: SQOOP-484.patch, SQOOP-484.patch
>
>
> This issue is continuation of JIRA ticket SQOOP-463. 
> I've investigated MySQL JDBC connector behavior in case of columns defined as TINYINT(1).
By default MySQL JDBC connector is converting TINYINT(1) into java.sql.Types.BIT, which can
be very easily turned off by specifying tinyInt1isBit=false in JDBC path. For example jdbc:mysql://localhost/test?tinyInt1isBit=false.
I would suggest to update troubleshooting guide by suggesting users to set this property rather
than overriding default sqoop type mapping.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message