spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Spark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-20718) FileSourceScanExec with different filter orders should be the same after canonicalization
Date Fri, 12 May 2017 07:06:04 GMT

    [ https://issues.apache.org/jira/browse/SPARK-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007721#comment-16007721
] 

Apache Spark commented on SPARK-20718:
--------------------------------------

User 'wzhfy' has created a pull request for this issue:
https://github.com/apache/spark/pull/17962

> FileSourceScanExec with different filter orders should be the same after canonicalization
> -----------------------------------------------------------------------------------------
>
>                 Key: SPARK-20718
>                 URL: https://issues.apache.org/jira/browse/SPARK-20718
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.2.0
>            Reporter: Zhenhua Wang
>            Assignee: Zhenhua Wang
>             Fix For: 2.2.0
>
>
> Since `constraints` in `QueryPlan` is a set, the order of filters can differ. Usually
this is ok because of canonicalization. However, in `FileSourceScanExec`, its data filters
and partition filters are sequences, and their orders are not canonicalized. So `def sameResult`
returns different results for different orders of data/partition filters. This leads to, e.g.
different decision for `ReuseExchange`, and thus results in unstable performance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message