[
https://issues.apache.org/jira/browse/SPARK-13668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameer Agarwal updated SPARK-13668:
-----------------------------------
Description:
If a filter predicate or a join condition consists of `IsNotNull` checks, we
should reorder these checks such that these non-nullability checks are
evaluated before the rest of the predicates.
For e.g., if a filter predicate is of the form `a > 5 && isNotNull(b)`, we
should rewrite this as `isNotNull(b) && a > 5` during physical plan generation.
cc [~nongli] [~yhuai]
was:
If a filter predicate or a join condition consists of `IsNotNull` checks, we
should reorder these checks such that these non-nullability checks are
evaluated before the rest of the predicates.
For e.g., if a filter predicate is of the form `a > 5 && isNotNull(b)`, we
should rewrite this as `isNotNull(b) && a` during physical plan generation.
cc [~nongli] [~yhuai]
> Reorder filter/join predicates to short-circuit isNotNull checks
> ----------------------------------------------------------------
>
> Key: SPARK-13668
> URL: https://issues.apache.org/jira/browse/SPARK-13668
> Project: Spark
> Issue Type: Improvement
> Reporter: Sameer Agarwal
>
> If a filter predicate or a join condition consists of `IsNotNull` checks, we
> should reorder these checks such that these non-nullability checks are
> evaluated before the rest of the predicates.
> For e.g., if a filter predicate is of the form `a > 5 && isNotNull(b)`, we
> should rewrite this as `isNotNull(b) && a > 5` during physical plan
> generation.
> cc [~nongli] [~yhuai]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
