diff options
| author | Herman van Hovell <hvanhovell@databricks.com> | 2016-11-04 21:18:13 +0100 |
|---|---|---|
| committer | Herman van Hovell <hvanhovell@databricks.com> | 2016-11-04 21:18:13 +0100 |
| commit | 550cd56e8b6addb26efe3ce16976c9c34fa0c832 (patch) | |
| tree | 3404f604e2772a2b3b80efdb6a24f36bd6465652 /scalastyle-config.xml | |
| parent | a42d738c5de08bd395a7c220c487146173c6c163 (diff) | |
| download | spark-550cd56e8b6addb26efe3ce16976c9c34fa0c832.tar.gz spark-550cd56e8b6addb26efe3ce16976c9c34fa0c832.tar.bz2 spark-550cd56e8b6addb26efe3ce16976c9c34fa0c832.zip | |
[SPARK-17337][SQL] Do not pushdown predicates through filters with predicate subqueries
## What changes were proposed in this pull request?
The `PushDownPredicate` rule can create a wrong result if we try to push a filter containing a predicate subquery through a project when the subquery and the project share attributes (have the same source).
The current PR fixes this by making sure that we do not push down when there is a predicate subquery that outputs the same attributes as the filters new child plan.
## How was this patch tested?
Added a test to `SubquerySuite`. nsyca has done previous work this. I have taken test from his initial PR.
Author: Herman van Hovell <hvanhovell@databricks.com>
Closes #15761 from hvanhovell/SPARK-17337.
Diffstat (limited to 'scalastyle-config.xml')
0 files changed, 0 insertions, 0 deletions