[
https://issues.apache.org/jira/browse/SQOOP-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286828#comment-14286828
]
ASF subversion and git services commented on SQOOP-2022:
--------------------------------------------------------
Commit 4ac3c3862bb0a7af3d300badbfe51cb43e0d097c in sqoop's branch
refs/heads/sqoop2 from [~abec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=4ac3c38 ]
SQOOP-2022: Sqoop2: SqoopIDFUtils uses bit size instead of byteSize to check
for INT/LONG/FLOAT/Double
(Veena Basavaraj via Abraham Elmahrek)
> 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-v3.patch,
> SQOOP-2022-v4.patch, SQOOP-2022-v5.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)
