[
https://issues.apache.org/jira/browse/SQOOP-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280527#comment-14280527
]
Sqoop QA bot commented on SQOOP-2022:
-------------------------------------
Testing file
[SQOOP-2022.patch|https://issues.apache.org/jira/secure/attachment/12692794/SQOOP-2022.patch]
against branch sqoop2 took 0:38:21.378300.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} Patch does not add/modifny any test case
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All unit tests passed
{color:green}SUCCESS:{color} All integration tests passed
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/943/console].
This message is automatically generated.
> 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.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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
