[jira] [Commented] (DRILL-2022) Parquet engine falls back to "new" Parquet reader unnecessarily

["Jason Altekruse (JIRA)" <ji...@apache.org>]

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

Jason Altekruse commented on DRILL-2022:
----------------------------------------

[~dragoncurve] Sorry this has been sitting around for so long. I will be taking a look at this and getting it merged in the next few days.

> Parquet engine falls back to "new" Parquet reader unnecessarily
> ---------------------------------------------------------------
>
>                 Key: DRILL-2022
>                 URL: https://issues.apache.org/jira/browse/DRILL-2022
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Storage - Parquet
>    Affects Versions: 0.8.0
>            Reporter: Adam Gilmore
>            Assignee: Jason Altekruse
>            Priority: Minor
>             Fix For: 0.9.0
>
>         Attachments: DRILL-2022.1.patch.txt, DRILL-2022.2.patch.txt
>
>
> The Parquet engine falls back to the "new" Parquet reader whenever a Parquet file that is "complex" (i.e. not purely primitive types) is found.
> The engine should still use the faster reader when all the projected columns are primitive types and only fall back to the other reader when columns containing complex types are selected.



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