[
https://issues.apache.org/jira/browse/SPARK-10334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Armbrust resolved SPARK-10334.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Issue resolved by pull request 8515
[https://github.com/apache/spark/pull/8515]
> Partitioned table scan's query plan does not show Filter and Project on top
> of the table scan
> ---------------------------------------------------------------------------------------------
>
> Key: SPARK-10334
> URL: https://issues.apache.org/jira/browse/SPARK-10334
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.5.0
> Reporter: Yin Huai
> Assignee: Yin Huai
> Priority: Critical
> Fix For: 1.5.0
>
>
> {code}
> Seq(Tuple2(1, 1), Tuple2(2, 2)).toDF("i",
> "j").write.format("parquet").partitionBy("i").save("/tmp/testFilter_partitioned")
> val df1 =
> sqlContext.read.format("parquet").load("/tmp/testFilter_partitioned")
> df1.selectExpr("hash(i)", "hash(j)").show
> df1.filter("hash(j) = 1").explain
> == Physical Plan ==
> Scan ParquetRelation[file:/tmp/testFilter_partitioned][j#20,i#21]
> {code}
> Looks like the reason is that we correctly apply the project and filter.
> Then, we create an RDD for the result and then manually create a PhysicalRDD.
> So, the Project and Filter on top of the original table scan disappears from
> the physical plan.
> See
> https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSourceStrategy.scala#L138-L175
> We will not generate wrong result. But, the query plan is confusing.
--
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
