You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Qian Xu (JIRA)" <ji...@apache.org> on 2015/01/16 18:27:34 UTC
[jira] [Commented] (SQOOP-2023) GenericJDBCConnector Handling
unsigned Ints is broken
[ https://issues.apache.org/jira/browse/SQOOP-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280525#comment-14280525 ]
Qian Xu commented on SQOOP-2023:
--------------------------------
A column is an unsigned int. According to MySQL documentation,
> INT,INTEGER[(M)] [UNSIGNED] INTEGER [UNSIGNED] java.lang.Integer, if UNSIGNED java.lang.Long
In SqoopIDFUtil, the handing {{toCSVFixedPoint}} can be problematic. Either check FixedPoint.getUnsigned() or use some loose valiation.
{code}
if (obj instanceof Long) {
// Unsigned integer will be be java.lang.Long
return ((Long) obj).toString();
} else {
return ((Integer) obj).toString();
}
{code}
> GenericJDBCConnector Handling unsigned Ints is broken
> -----------------------------------------------------
>
> Key: SQOOP-2023
> URL: https://issues.apache.org/jira/browse/SQOOP-2023
> Project: Sqoop
> Issue Type: Bug
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
>
> this issue started from SQOOP-2018, more details are in that ticket in the end of the comments section
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)