You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Kathleen Ting (Created) (JIRA)" <ji...@apache.org> on 2012/03/14 23:34:40 UTC
[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
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
[jira] [Commented] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229741#comment-13229741 ]
jiraposter@reviews.apache.org commented on SQOOP-463:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4357/
-----------------------------------------------------------
(Updated 2012-03-14 23:08:50.341102)
Review request for Sqoop and Arvind Prabhakar.
Summary
-------
Updated documentation.
This addresses bug SQOOP-463.
https://issues.apache.org/jira/browse/SQOOP-463
Diffs (updated)
-----
./src/docs/user/troubleshooting.txt 1300726
Diff: https://reviews.apache.org/r/4357/diff
Testing
-------
Built docs and verified.
Thanks,
Kathleen
> 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
> Attachments: SQOOP-463-1.patch, SQOOP-463.patch
>
>
> 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
[jira] [Updated] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "Kathleen Ting (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathleen Ting updated SQOOP-463:
--------------------------------
Attachment: SQOOP-463-2.patch
Added use case of non-Hive import to HDFS.
> 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
> Attachments: SQOOP-463-1.patch, SQOOP-463-2.patch, SQOOP-463.patch
>
>
> 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
[jira] [Commented] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229716#comment-13229716 ]
jiraposter@reviews.apache.org commented on SQOOP-463:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4357/
-----------------------------------------------------------
Review request for Sqoop and Arvind Prabhakar.
Summary
-------
Updated documentation.
This addresses bug SQOOP-463.
https://issues.apache.org/jira/browse/SQOOP-463
Diffs
-----
./src/docs/user/troubleshooting.txt 1300726
Diff: https://reviews.apache.org/r/4357/diff
Testing
-------
Built docs and verified.
Thanks,
Kathleen
> 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
> Attachments: SQOOP-463.patch
>
>
> 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
[jira] [Commented] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "Jarek Jarcec Cecho (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230263#comment-13230263 ]
Jarek Jarcec Cecho commented on SQOOP-463:
------------------------------------------
I personally believe that mapping TINYINT(1) to java.sql.Types.BIT might be a bug in MySQL JDBC connector. As far as I know, the length field in numeric types in MySQL is only used for setting default display width and it's not related to actual data size. So that column with TINYINT(1) might contains higher values than 1. I was able to verify this piece of information in MySQL manual (see [1]) and live in running server (see [2]).
[1] http://dev.mysql.com/doc/refman/5.6/en/numeric-type-overview.html
[2] MySQL calls:
mysql> create table pokus(col tinyint(1));
Query OK, 0 rows affected (0.06 sec)
mysql> describe pokus;
+-------+------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------+------------+------+-----+---------+-------+
| col | tinyint(1) | YES | | NULL | |
+-------+------------+------+-----+---------+-------+
1 row in set (0.00 sec)
mysql> insert into pokus values(1);
Query OK, 1 row affected (0.00 sec)
mysql> insert into pokus values(2);
Query OK, 1 row affected (0.00 sec)
mysql> insert into pokus values(3);
Query OK, 1 row affected (0.00 sec)
mysql> insert into pokus values(10);
Query OK, 1 row affected (0.00 sec)
mysql> select * from pokus;
+------+
| col |
+------+
| 1 |
| 2 |
| 3 |
| 10 |
+------+
4 rows in set (0.00 sec)
> 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
> Attachments: SQOOP-463-1.patch, SQOOP-463.patch
>
>
> 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
[jira] [Commented] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235836#comment-13235836 ]
Hudson commented on SQOOP-463:
------------------------------
Integrated in Sqoop-ant-jdk-1.6 #99 (See [https://builds.apache.org/job/Sqoop-ant-jdk-1.6/99/])
SQOOP-463. Sqoop User Guide's troubleshooting section should explain how to override the column mapping when importing a table from MySQL into Hive.
(Kathleen Ting via Jarek Jarcec Cecho) (Revision 1303911)
Result = SUCCESS
jarcec : http://svn.apache.org/viewvc/?view=rev&rev=1303911
Files :
* /incubator/sqoop/trunk/src/docs/user/troubleshooting.txt
> 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
> Fix For: 1.4.2-incubating
>
> Attachments: SQOOP-463-1.patch, SQOOP-463-2.patch, SQOOP-463.patch
>
>
> 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
[jira] [Commented] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234028#comment-13234028 ]
jiraposter@reviews.apache.org commented on SQOOP-463:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4357/
-----------------------------------------------------------
(Updated 2012-03-21 01:49:19.048841)
Review request for Sqoop and Jarek Cecho.
Changes
-------
Added use case of non-Hive import to HDFS.
Summary
-------
Updated documentation.
This addresses bug SQOOP-463.
https://issues.apache.org/jira/browse/SQOOP-463
Diffs (updated)
-----
./src/docs/user/troubleshooting.txt 1300726
Diff: https://reviews.apache.org/r/4357/diff
Testing
-------
Built docs and verified.
Thanks,
Kathleen
> 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
> Attachments: SQOOP-463-1.patch, SQOOP-463.patch
>
>
> 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
[jira] [Issue Comment Edited] (SQOOP-463) Sqoop User Guide's
troubleshooting section should explain how to override the column mapping
when importing a table from MySQL into Hive
Posted by "Jarek Jarcec Cecho (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230263#comment-13230263 ]
Jarek Jarcec Cecho edited comment on SQOOP-463 at 3/16/12 8:11 AM:
-------------------------------------------------------------------
I personally believe that mapping TINYINT(1) to java.sql.Types.BIT might be a bug in MySQL JDBC connector. As far as I know, the length field in numeric types in MySQL is only used for setting default display width and it's not related to actual data size. So that column with TINYINT(1) might contain higher values than 1. I was able to verify this piece of information in MySQL manual (see [1]) and live in running server (see [2]).
[1] http://dev.mysql.com/doc/refman/5.6/en/numeric-type-overview.html
[2] MySQL calls:
mysql> create table pokus(col tinyint(1));
Query OK, 0 rows affected (0.06 sec)
mysql> describe pokus;
+-------+------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------+------------+------+-----+---------+-------+
| col | tinyint(1) | YES | | NULL | |
+-------+------------+------+-----+---------+-------+
1 row in set (0.00 sec)
mysql> insert into pokus values(1);
Query OK, 1 row affected (0.00 sec)
mysql> insert into pokus values(2);
Query OK, 1 row affected (0.00 sec)
mysql> insert into pokus values(3);
Query OK, 1 row affected (0.00 sec)
mysql> insert into pokus values(10);
Query OK, 1 row affected (0.00 sec)
mysql> select * from pokus;
+------+
| col |
+------+
| 1 |
| 2 |
| 3 |
| 10 |
+------+
4 rows in set (0.00 sec)
was (Author: jarcec):
I personally believe that mapping TINYINT(1) to java.sql.Types.BIT might be a bug in MySQL JDBC connector. As far as I know, the length field in numeric types in MySQL is only used for setting default display width and it's not related to actual data size. So that column with TINYINT(1) might contains higher values than 1. I was able to verify this piece of information in MySQL manual (see [1]) and live in running server (see [2]).
[1] http://dev.mysql.com/doc/refman/5.6/en/numeric-type-overview.html
[2] MySQL calls:
mysql> create table pokus(col tinyint(1));
Query OK, 0 rows affected (0.06 sec)
mysql> describe pokus;
+-------+------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------+------------+------+-----+---------+-------+
| col | tinyint(1) | YES | | NULL | |
+-------+------------+------+-----+---------+-------+
1 row in set (0.00 sec)
mysql> insert into pokus values(1);
Query OK, 1 row affected (0.00 sec)
mysql> insert into pokus values(2);
Query OK, 1 row affected (0.00 sec)
mysql> insert into pokus values(3);
Query OK, 1 row affected (0.00 sec)
mysql> insert into pokus values(10);
Query OK, 1 row affected (0.00 sec)
mysql> select * from pokus;
+------+
| col |
+------+
| 1 |
| 2 |
| 3 |
| 10 |
+------+
4 rows in set (0.00 sec)
> 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
> Attachments: SQOOP-463-1.patch, SQOOP-463.patch
>
>
> 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
[jira] [Commented] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234167#comment-13234167 ]
jiraposter@reviews.apache.org commented on SQOOP-463:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4357/#review6167
-----------------------------------------------------------
Ship it!
Thank you for the change Kate!
- Jarek
On 2012-03-21 01:49:19, Kathleen Ting wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/4357/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-03-21 01:49:19)
bq.
bq.
bq. Review request for Sqoop and Jarek Cecho.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Updated documentation.
bq.
bq.
bq. This addresses bug SQOOP-463.
bq. https://issues.apache.org/jira/browse/SQOOP-463
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. ./src/docs/user/troubleshooting.txt 1300726
bq.
bq. Diff: https://reviews.apache.org/r/4357/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Built docs and verified.
bq.
bq.
bq. Thanks,
bq.
bq. Kathleen
bq.
bq.
> 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
> Attachments: SQOOP-463-1.patch, SQOOP-463.patch
>
>
> 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
[jira] [Commented] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233725#comment-13233725 ]
jiraposter@reviews.apache.org commented on SQOOP-463:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4357/#review6138
-----------------------------------------------------------
I did not yet try how MySQL JDBC driver will behave myself, but column defined as TINYINT(1) might contain valid values in range 0-255 (in unsigned form). So if the driver is reporting type BIT for such columns, then there must be some data truncation. Therefore I would suggest extending this new section also for normal (non-hive) import case.
- Jarek
On 2012-03-20 20:10:41, Kathleen Ting wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/4357/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-03-20 20:10:41)
bq.
bq.
bq. Review request for Sqoop and Jarek Cecho.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Updated documentation.
bq.
bq.
bq. This addresses bug SQOOP-463.
bq. https://issues.apache.org/jira/browse/SQOOP-463
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. ./src/docs/user/troubleshooting.txt 1300726
bq.
bq. Diff: https://reviews.apache.org/r/4357/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Built docs and verified.
bq.
bq.
bq. Thanks,
bq.
bq. Kathleen
bq.
bq.
> 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
> Attachments: SQOOP-463-1.patch, SQOOP-463.patch
>
>
> 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
[jira] [Updated] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "Kathleen Ting (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathleen Ting updated SQOOP-463:
--------------------------------
Status: Patch Available (was: Open)
> 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
> Attachments: SQOOP-463.patch
>
>
> 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
[jira] [Updated] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "Kathleen Ting (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathleen Ting updated SQOOP-463:
--------------------------------
Attachment: SQOOP-463-1.patch
Fixed typo (missing space between two words). Thanks to Cheolsoo for catching that.
> 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
> Attachments: SQOOP-463-1.patch, SQOOP-463.patch
>
>
> 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
[jira] [Updated] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "Kathleen Ting (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathleen Ting updated SQOOP-463:
--------------------------------
Attachment: SQOOP-463.patch
> 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
> Attachments: SQOOP-463.patch
>
>
> 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
[jira] [Updated] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "Jarek Jarcec Cecho (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Jarcec Cecho updated SQOOP-463:
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.4.2-incubating
Status: Resolved (was: Patch Available)
Patch committed, thank you Kate!
> 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
> Fix For: 1.4.2-incubating
>
> Attachments: SQOOP-463-1.patch, SQOOP-463-2.patch, SQOOP-463.patch
>
>
> 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
[jira] [Commented] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233709#comment-13233709 ]
jiraposter@reviews.apache.org commented on SQOOP-463:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4357/
-----------------------------------------------------------
(Updated 2012-03-20 20:10:41.312155)
Review request for Sqoop and Jarek Cecho.
Summary
-------
Updated documentation.
This addresses bug SQOOP-463.
https://issues.apache.org/jira/browse/SQOOP-463
Diffs
-----
./src/docs/user/troubleshooting.txt 1300726
Diff: https://reviews.apache.org/r/4357/diff
Testing
-------
Built docs and verified.
Thanks,
Kathleen
> 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
> Attachments: SQOOP-463-1.patch, SQOOP-463.patch
>
>
> 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
[jira] [Commented] (SQOOP-463) Sqoop User Guide's troubleshooting
section should explain how to override the column mapping when importing a
table from MySQL into Hive
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229723#comment-13229723 ]
jiraposter@reviews.apache.org commented on SQOOP-463:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4357/#review5969
-----------------------------------------------------------
Ship it!
+1
./src/docs/user/troubleshooting.txt
<https://reviews.apache.org/r/4357/#comment12943>
It looks like space is missing between TINYINT(1) and datatype.
- Cheolsoo
On 2012-03-14 22:47:39, Kathleen Ting wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/4357/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-03-14 22:47:39)
bq.
bq.
bq. Review request for Sqoop and Arvind Prabhakar.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Updated documentation.
bq.
bq.
bq. This addresses bug SQOOP-463.
bq. https://issues.apache.org/jira/browse/SQOOP-463
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. ./src/docs/user/troubleshooting.txt 1300726
bq.
bq. Diff: https://reviews.apache.org/r/4357/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Built docs and verified.
bq.
bq.
bq. Thanks,
bq.
bq. Kathleen
bq.
bq.
> 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
> Attachments: SQOOP-463.patch
>
>
> 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