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

ASF GitHub Bot commented on DRILL-5846:
---------------------------------------

Github user sachouche commented on a diff in the pull request:

    https://github.com/apache/drill/pull/1060#discussion_r161065237
  
    --- Diff: protocol/src/main/protobuf/UserBitShared.proto ---
    @@ -148,6 +148,8 @@ message SerializedField {
       optional int32 value_count = 4;
       optional int32 var_byte_length = 5;
       optional int32 buffer_length = 7;
    +  optional bool is_dup = 8;
    +  optional int32 logical_value_count = 9;
    --- End diff --
    
    Just had an offline conversation with Paul and Kunal. The agreement is that 
we should introduce a versioning mechanism at the protocol level so that 
clients could advertise their version identifier; this way the server can use 
this information to turn on / off features based on the client capabilities. 
The task is only to create the preliminary versioning infrastructure; more 
sophistication can be added later on. 


> Improve Parquet Reader Performance for Flat Data types 
> -------------------------------------------------------
>
>                 Key: DRILL-5846
>                 URL: https://issues.apache.org/jira/browse/DRILL-5846
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Storage - Parquet
>    Affects Versions: 1.11.0
>            Reporter: salim achouche
>            Assignee: salim achouche
>              Labels: performance
>             Fix For: 1.13.0
>
>
> The Parquet Reader is a key use-case for Drill. This JIRA is an attempt to 
> further improve the Parquet Reader performance as several users reported that 
> Parquet parsing represents the lion share of the overall query execution. It 
> tracks Flat Data types only as Nested DTs might involve functional and 
> processing enhancements (e.g., a nested column can be seen as a Document; 
> user might want to perform operations scoped at the document level that is no 
> need to span all rows). Another JIRA will be created to handle the nested 
> columns use-case.



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

Reply via email to