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

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

jbimbert commented on issue #1298: DRILL-5796: Filter pruning for multi 
rowgroup parquet file
URL: https://github.com/apache/drill/pull/1298#issuecomment-396262789
 
 
   Tests DRILL_6259 are now OK. 
   The issue came from a query of the form "select * from t where t.col[2] > 
1", where col[] is an array; in this case, we can't deduce the value of the 
column from the metadata of the row group, especially is col[2] is null for 
example.
   To correct this issue, I chose to set filter result as ROWS_MATCH.SOME 
instead of ROWS_MATCH.ALL for array columns only.
   This should impact only queries on array columns, which will run as usual 
(with no filter pruning).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Filter pruning for multi rowgroup parquet file
> ----------------------------------------------
>
>                 Key: DRILL-5796
>                 URL: https://issues.apache.org/jira/browse/DRILL-5796
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Storage - Parquet
>            Reporter: Damien Profeta
>            Assignee: Jean-Blas IMBERT
>            Priority: Major
>             Fix For: 1.14.0
>
>
> Today, filter pruning use the file name as the partitioning key. This means 
> you can remove a partition only if the whole file is for the same partition. 
> With parquet, you can prune the filter if the rowgroup make a partition of 
> your dataset as the unit of work if the rowgroup not the file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to