GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/17679
[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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/viirya/spark-1 SPARK-20356
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/17679.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #17679
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
