sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathleen Ting (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-463) Sqoop User Guide's troubleshooting section should explain how to override the column mapping when importing a table from MySQL into Hive
Date Wed, 14 Mar 2012 22:34:40 GMT
Sqoop User Guide's troubleshooting section should explain how to override the column mapping
when importing a table from MySQL into Hive
----------------------------------------------------------------------------------------------------------------------------------------

                 Key: SQOOP-463
                 URL: https://issues.apache.org/jira/browse/SQOOP-463
             Project: Sqoop
          Issue Type: Improvement
          Components: docs
    Affects Versions: 1.4.1-incubating
            Reporter: Kathleen Ting
            Assignee: Kathleen Ting


When importing a table from MySQL into Hive where one of the columns is of datatype TINYINT(1),
Sqoop will automatically map this to the Hive datatype boolean. This is because the MySQL
JDBC connector maps the TINYINT(1) datatype to java.sql.Types.BIT, which Sqoop by default
maps to the Hive type Boolean. Consequently, if you have values such as 1 or 0 in this column,
they will fail to parse correctly in Hive, instead appearing as all NULL values.

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