You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2017/09/07 05:47:00 UTC
[jira] [Resolved] (IMPALA-5888) Parquet scanner does not free local
allocations for min/max and dictionary filters
[ https://issues.apache.org/jira/browse/IMPALA-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-5888.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.11.0
IMPALA-5888: free other local allocations in Parquet
Testing:
I wasn't able to produce any abnormal memory consumption from dictionary
or min/max filters so haven't included a regression test.
Change-Id: I7792552510b54aa95044e44218e3351a36d6f9a8
Reviewed-on: http://gerrit.cloudera.org:8080/7933
Reviewed-by: Tim Armstrong <ta...@cloudera.com>
Tested-by: Impala Public Jenkins
> Parquet scanner does not free local allocations for min/max and dictionary filters
> ----------------------------------------------------------------------------------
>
> Key: IMPALA-5888
> URL: https://issues.apache.org/jira/browse/IMPALA-5888
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.9.0, Impala 2.10.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Fix For: Impala 2.11.0
>
>
> This is the same issues as IMPALA-5885, but for the other conjuncts. I think min/max conjuncts are unlikely to be problematic now since they're evaluated once per row group, but we could accumulate a lot of memory from dictionary conjuncts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)