[
https://issues.apache.org/jira/browse/SQOOP-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-2022:
-----------------------------------
Description:
>From SQOOP-2018, [~stanleyxu2005] found a good issue we have where we use BIT
>SIZE instead of BYTE size. we have to fix this.
was:
treat INT as 4 bytes since both MySQL and Oracle and Postgres do it so
http://dev.mysql.com/doc/refman/5.0/en/integer-types.html
https://docs.oracle.com/cd/E17952_01/refman-5.5-en/storage-requirements.html
http://www.postgresql.org/docs/9.1/static/datatype-numeric.html
> 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
>
>
> From SQOOP-2018, [~stanleyxu2005] found a good issue we have where we use BIT
> SIZE instead of BYTE size. we have to fix this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
