You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2017/05/12 06:00:14 UTC
[jira] [Resolved] (SPARK-20718) FileSourceScanExec with different
filter orders should be the same after canonicalization
[ https://issues.apache.org/jira/browse/SPARK-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-20718.
---------------------------------
Resolution: Fixed
Assignee: Zhenhua Wang
Fix Version/s: 2.2.0
> 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