-
- Downloads
[SPARK-15381] [SQL] physical object operator should define reference correctly
## What changes were proposed in this pull request? Whole Stage Codegen depends on `SparkPlan.reference` to do some optimization. For physical object operators, they should be consistent with their logical version and set the `reference` correctly. ## How was this patch tested? new test in DatasetSuite Author: Wenchen Fan <wenchen@databricks.com> Closes #13167 from cloud-fan/bug.
Showing
- sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/object.scala 5 additions, 5 deletions.../org/apache/spark/sql/catalyst/plans/logical/object.scala
- sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala 1 addition, 1 deletion...cala/org/apache/spark/sql/execution/SparkStrategies.scala
- sql/core/src/main/scala/org/apache/spark/sql/execution/objects.scala 53 additions, 41 deletions...c/main/scala/org/apache/spark/sql/execution/objects.scala
- sql/core/src/test/scala/org/apache/spark/sql/DatasetSuite.scala 5 additions, 0 deletions...re/src/test/scala/org/apache/spark/sql/DatasetSuite.scala
Loading
Please register or sign in to comment