You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Gabor Szadovszky (JIRA)" <ji...@apache.org> on 2018/04/21 12:39:04 UTC
[jira] [Updated] (PARQUET-654) Make record-level filtering optional
[ https://issues.apache.org/jira/browse/PARQUET-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Szadovszky updated PARQUET-654:
-------------------------------------
Fix Version/s: 1.8.2
> Make record-level filtering optional
> ------------------------------------
>
> Key: PARQUET-654
> URL: https://issues.apache.org/jira/browse/PARQUET-654
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-mr
> Reporter: Cheng Lian
> Assignee: Ryan Blue
> Priority: Major
> Fix For: 1.9.0, 1.8.2
>
>
> For some engines, especially those with vectorized Parquet readers, filter predicate can often be evaluated more efficiently by the engine. In these cases, Parquet record-level filtering may even slow down query execution when filter push-down is enabled. On the other hand, when the data is well prepared, filter push-down can be very valuable due to row group level filtering.
> One possible improvement here is to add a configuration option that makes record-level filtering optional. In this way, the upper-level engine may leverage both Parquet row group level filtering and faster native record-level filtering.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)