-
- Downloads
[SPARK-20356][SQL] Pruned InMemoryTableScanExec should have correct output...
[SPARK-20356][SQL] Pruned InMemoryTableScanExec should have correct output partitioning and ordering ## What changes were proposed in this pull request? The output of `InMemoryTableScanExec` can be pruned and mismatch with `InMemoryRelation` and its child plan's output. This causes wrong output partitioning and ordering. ## How was this patch tested? Jenkins tests. Please review http://spark.apache.org/contributing.html before opening a pull request. Author: Liang-Chi Hsieh <viirya@gmail.com> Closes #17679 from viirya/SPARK-20356.
Showing
- sql/core/src/main/scala/org/apache/spark/sql/execution/columnar/InMemoryTableScanExec.scala 3 additions, 1 deletion.../spark/sql/execution/columnar/InMemoryTableScanExec.scala
- sql/core/src/test/scala/org/apache/spark/sql/execution/columnar/InMemoryColumnarQuerySuite.scala 15 additions, 0 deletions...k/sql/execution/columnar/InMemoryColumnarQuerySuite.scala
Loading
Please register or sign in to comment