Burak Gursoy created SQOOP-2510:
-----------------------------------
Summary: Documentation bug about MySQL unsigned int
Key: SQOOP-2510
URL: https://issues.apache.org/jira/browse/SQOOP-2510
Project: Sqoop
Issue Type: Bug
Reporter: Burak Gursoy
Priority: Trivial
Hi,
First the disclaimer: I am not experiencing the behaviour described in the
documentation with:
Sqoop 1.4.5-cdh5.4.3
MySQL: 5.6.17-log
Now the details:
There is this section about MySQL (sorry I'll use the mirror link(s) as it's
handy):
https://github.com/apache/sqoop/blob/trunk/src/docs/user/compatibility.txt#L107
"+UNSIGNED+ columns
^^^^^^^^^^^^^^^^^^
Columns with type +UNSIGNED+ in MySQL can hold values between 0 and
2^32 (+4294967295+), but the database will report the data type to Sqoop
as +INTEGER+, which will can hold values between +-2147483648+ and
+\+2147483647+. Sqoop cannot currently import +UNSIGNED+ values above
+2147483647+."
I see that there was a fix for that 4 years ago, but perhaps the MySQL version
tried at the time had a bug in it too (no version specified in the doc).
https://github.com/apache/sqoop/commit/fd3634dc3c6568c5d1f3515e8f47b474805b5809
I think that this section is misleading and either needs to be removed or a
specific Sqoop+MySQL version combination needs to be specified in there.
However, since the versions were not specified back then:
https://github.com/apache/sqoop/commit/faabc51a90b5c8a72c33973f91d14a84365cd3e5
I think this information is long lost and really referring to archaic versions
of both.
Thanks,
Burak
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
