[
https://issues.apache.org/jira/browse/SQOOP-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284168#comment-14284168
]
Jarek Jarcec Cecho commented on SQOOP-2022:
-------------------------------------------
I do like the option 2) as well. The fact that we won't cover the case when
MySQL unsigned long will get out of bounds seems as a reasonable limitation for
Generic JDBC Connector - I believe that MySQL is the only database that I've
looked back when exploring types for SQOOP-515 that do supports unsigned types.
> Sqoop2: SqoopIDFUtils uses bit size instead of byteSize to check for
> INT/LONG/FLOAT/Double
> ------------------------------------------------------------------------------------------
>
> Key: SQOOP-2022
> URL: https://issues.apache.org/jira/browse/SQOOP-2022
> Project: Sqoop
> Issue Type: Bug
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: SQOOP-2022-v1.patch, SQOOP-2022.patch
>
>
> From SQOOP-2018, [~stanleyxu2005] found a good issue we have where we use BIT
> SIZE instead of BYTE size. we have to fix this.
> also see https://issues.apache.org/jira/browse/SQOOP-2023 to get more context
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
