You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2014/12/20 04:12:13 UTC
[jira] [Commented] (SPARK-4493) Don't pushdown Eq, NotEq, Lt, LtEq,
Gt and GtEq predicates with nulls for Parquet
[ https://issues.apache.org/jira/browse/SPARK-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254484#comment-14254484 ]
Apache Spark commented on SPARK-4493:
-------------------------------------
User 'liancheng' has created a pull request for this issue:
https://github.com/apache/spark/pull/3748
> Don't pushdown Eq, NotEq, Lt, LtEq, Gt and GtEq predicates with nulls for Parquet
> ---------------------------------------------------------------------------------
>
> Key: SPARK-4493
> URL: https://issues.apache.org/jira/browse/SPARK-4493
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.1.0
> Reporter: Cheng Lian
> Assignee: Cheng Lian
> Fix For: 1.3.0
>
>
> Predicates like {{a = NULL}} and {{a < NULL}} can't be pushed down since Parquet {{Lt}}, {{LtEq}}, {{Gt}}, {{GtEq}} doesn't accept null value. Not that {{Eq}} and {{NotEq}} can only be used with {{null}} to represent predicates like {{a IS NULL}} and {{a IS NOT NULL}}.
> However, normally this issue doesn't cause NPE because any value compared to {{NULL}} results {{NULL}}, and Spark SQL automatically optimizes out {{NULL}} predicate in the {{SimplifyFilters}} rule. Only testing code that intentionally disables the optimizer may trigger this issue. (That's why this issue is not marked as blocker).
--
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