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

Arina Ielchiieva commented on DRILL-4746:
-----------------------------------------

[~rkins],
Root case: when adding multibyte line support 
TextInput.updateLengthBasedOnConstraint was refactored with mistakes, which 
lead to incorrect determination of line delimiter position when file was 
split., which in fact lead to some data loss. That's why issue was reproduced 
on maprfs but not on local fs (where files aren't split). 
Fix: I have refactored TextInput.updateLengthBasedOnConstraint from scratch 
more thoroughly.




> Verification Failures (Decimal values) in drill's regression tests
> ------------------------------------------------------------------
>
>                 Key: DRILL-4746
>                 URL: https://issues.apache.org/jira/browse/DRILL-4746
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Data Types, Storage - Text & CSV
>    Affects Versions: 1.7.0
>            Reporter: Rahul Challapalli
>            Assignee: Arina Ielchiieva
>            Priority: Critical
>             Fix For: 1.8.0
>
>
> We started seeing the below 4 functional test failures in drill's extended 
> tests [1]. The data for the below tests can be downloaded from [2]
> {code}
> framework/resources/Functional/aggregates/tpcds_variants/text/aggregate28.q
> framework/resources/Functional/tpcds/impala/text/q43.q
> framework/resources/Functional/tpcds/variants/text/q6_1.sql
> framework/resources/Functional/aggregates/tpcds_variants/text/aggregate29.q
> {code}
> The failures started showing up from the commit [3]
> [1] https://github.com/mapr/drill-test-framework
> [2] http://apache-drill.s3.amazonaws.com/files/tpcds-sf1-text.tgz
> [3] 
> https://github.com/apache/drill/commit/223507b76ff6c2227e667ae4a53f743c92edd295
> Let me know if more information is needed to reproduce this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to