[jira] [Resolved] (SPARK-16343) Improve the PushDownPredicate rule to pushdown predicates currectly in non-deterministic condition

["Cheng Lian (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-16343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cheng Lian resolved SPARK-16343.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0

Issue resolved by pull request 14012
[https://github.com/apache/spark/pull/14012]

> Improve the PushDownPredicate rule to pushdown predicates currectly in non-deterministic condition
> --------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-16343
>                 URL: https://issues.apache.org/jira/browse/SPARK-16343
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 1.6.2
>            Reporter: Jiang Xingbo
>            Priority: Critical
>             Fix For: 2.1.0
>
>
> Currently our Optimizer may reorder the predicates to run them more efficient, but in non-deterministic condition, change the order between deterministic parts and non-deterministic parts may change the number of input rows. For example:
> {code:sql}
> SELECT a FROM t WHERE rand() < 0.1 AND a = 1
> {code}
> And
> {code:sql}
> SELECT a FROM t WHERE a = 1 AND rand() < 0.1
> {code}
> may call rand() for different times and therefore the output rows differ.



--
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