[ 
https://issues.apache.org/jira/browse/SQOOP-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145272#comment-16145272
 ] 

ASF subversion and git services commented on SQOOP-3195:
--------------------------------------------------------

Commit 1378520e498595bc46002395f2d50412a42a1df3 in sqoop's branch 
refs/heads/trunk from [~BoglarkaEgyed]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=1378520 ]

SQOOP-3195: SQLServerDatatypeImportDelimitedFileTest can fail in some 
environments

(Szabolcs Vasas via Boglarka Egyed)


> SQLServerDatatypeImportDelimitedFileTest can fail in some environments
> ----------------------------------------------------------------------
>
>                 Key: SQOOP-3195
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3195
>             Project: Sqoop
>          Issue Type: Test
>            Reporter: Szabolcs Vasas
>            Assignee: Szabolcs Vasas
>         Attachments: SQOOP-3195.patch
>
>
> I tried to execute the SQLServer third party tests with two different SQL 
> Server versions. With SQL Server 2014 Express edition all the tests were 
> successful however with SQL Server 2017 Developer edition I got the following 
> error:
> [junit] Test 
> org.apache.sqoop.manager.sqlserver.SQLServerDatatypeImportDelimitedFileTest 
> FAILED
>   Failure for following Test Data :
>   FLOAT
>   SCALE : null
>   PREC : null
>   TO_INSERT : 1.7976931348623157
>   DB_READBACK : 1.7976931348623155
>   HDFS_READBACK : 1.7976931348623155
>   NEG_POS_FLAG : POS
>   OFFSET : 8
>   -----------------------------------------------------------
>   Exception details :
>    expected a different string expected:<1.797693134862315[5]> but 
> was:<1.797693134862315[7]>
> By looking at the test case I have found that it inserts 1.7976931348623157 
> into the database but it expects 1.7976931348623155 (the last digit is 5 
> instead of 7) probably because float is an approximate numeric data types on 
> MSSQL and on earlier versions this is how it worked but.
> I suggest using a less precise float number in this test case to avoid 
> flakyness.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to