You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Arina Ielchiieva (JIRA)" <ji...@apache.org> on 2019/08/09 12:53:00 UTC

[jira] [Comment Edited] (DRILL-6528) Planner setting the wrong number of records to read (Parquet Reader)

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

Arina Ielchiieva edited comment on DRILL-6528 at 8/9/19 12:52 PM:
------------------------------------------------------------------

Most likely issue was fixed in DRILL-6857.


was (Author: arina):
Most like issue was fixed in DRILL-6857.

> Planner setting the wrong number of records to read (Parquet Reader)
> --------------------------------------------------------------------
>
>                 Key: DRILL-6528
>                 URL: https://issues.apache.org/jira/browse/DRILL-6528
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Query Planning &amp; Optimization
>            Reporter: salim achouche
>            Assignee: Arina Ielchiieva
>            Priority: Major
>             Fix For: 1.17.0
>
>
> - Recently fixed the Flat Parquet reader to honor the number of records to read
>  - Though few tests failed:
> TestUnionDistinct.testUnionDistinctEmptySides:356 Different number of records returned expected:<5> but was:<1>
> TestUnionAll.testUnionAllEmptySides:355 Different number of records returned expected:<5> but was:<1>
>  - I debugged one of them and realized the Planner was setting the wrong number of rows to read (in this case, one)
>  - You can put a break point and see this happening:
> Class: ParquetGroupScan
> Method: updateRowGroupInfo(long maxRecords)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)