spark-instrumented-optimizer/sql/core/src
Liang-Chi Hsieh 773754b6c1 [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.
2017-04-19 16:01:28 +08:00
..
main [SPARK-20356][SQL] Pruned InMemoryTableScanExec should have correct output partitioning and ordering 2017-04-19 16:01:28 +08:00
test [SPARK-20356][SQL] Pruned InMemoryTableScanExec should have correct output partitioning and ordering 2017-04-19 16:01:28 +08:00