[
https://issues.apache.org/jira/browse/SQOOP-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280551#comment-14280551
]
Veena Basavaraj edited comment on SQOOP-2023 at 1/16/15 5:53 PM:
-----------------------------------------------------------------
I think the right way is use the unsigned/ signed we have in the
Fixedpoint/Column, It exists for a reason. We should use it.
and this fix will be done in SQOOP-2022.
But the real interesting thing to me in what will the connectors do, when will
they set signed to true and unsigned to true:)
One way is to set the INTEGER to 8L, since it is the max value it can handle
with both signed and unsigned. so connectors have to be very careful about this
was (Author: vybs):
I think the right way is use the unsigned/ signed we have in the
Fixedpoint/Column, It exists for a reason. We should use it.
and this fix will be done in SQOOP-2022.
But the real interesting thing to me in what will the connectors do, when will
they set signed to true and unsigned to true:)
> 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)
