GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/20094
[SPARK-20392][SQL][followup] should not add extra AnalysisBarrier
## What changes were proposed in this pull request?
I found this problem while auditing the analyzer code. It's dangerous to
introduce extra `AnalysisBarrer` during analysis, as the plan inside it will
bypass all analysis afterward, which may not be expected.
## How was this patch tested?
existing tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloud-fan/spark barrier
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/20094.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 #20094
----
commit 64709fc78ad49d2dd260d8f3a7a96d10f0081cbb
Author: Wenchen Fan <wenchen@...>
Date: 2017-12-27T18:54:50Z
should not add extra AnalysisBarrier
----
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
