You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Lian (JIRA)" <ji...@apache.org> on 2015/08/12 14:06:46 UTC
[jira] [Resolved] (SPARK-9407) Parquet shouldn't fail when pushing
down predicates over a column whose underlying Parquet type is an ENUM
[ https://issues.apache.org/jira/browse/SPARK-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheng Lian resolved SPARK-9407.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Issue resolved by pull request 8107
[https://github.com/apache/spark/pull/8107]
> Parquet shouldn't fail when pushing down predicates over a column whose underlying Parquet type is an ENUM
> ----------------------------------------------------------------------------------------------------------
>
> Key: SPARK-9407
> URL: https://issues.apache.org/jira/browse/SPARK-9407
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.5.0
> Reporter: Cheng Lian
> Assignee: Cheng Lian
> Priority: Blocker
> Fix For: 1.5.0
>
>
> Spark SQL doesn't have an equivalent data type to Parquet {{BINARY (ENUM)}}, and always treats it as a UTF-8 encoded {{StringType}}. Thus, predicate over a Parquet {{ENUM}} column may be pushed down. However, Parquet 1.7.0 and prior versions only support filter push-down optimization for [a limited set of data types|https://github.com/apache/parquet-mr/blob/apache-parquet-1.7.0/parquet-column/src/main/java/org/apache/parquet/filter2/predicate/ValidTypeMap.java#L66-L80], and fails the query.
> The simplest solution seems to be upgrading parquet-mr to 1.8.1, which fixes this issue via PARQUET-201
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org