GitHub user dilipbiswal opened a pull request:
https://github.com/apache/spark/pull/17214
[SQL][MINOR] The analyzer rules are fired twice for cases when
AnalysisException is raised from analyzer.
## What changes were proposed in this pull request?
In general we have a checkAnalysis phase which validates the logical plan
and throw AnalysisException on semantic errors. However we also can throw
AnalysisException from a few analyzer rules like ResolveSubquery.
I found that we fire up the analyzer rule twice for the queries that throw
AnalysisException from one of the analyzer rules. This is a very minor fix. We
don't have to strictly fix it. I just got confused seeing the rule getting
fired two times when i was not expecting it.
## How was this patch tested?
Tested manually.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dilipbiswal/spark analyis_twice
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/17214.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 #17214
----
commit 86582ef421818110a3c2f4705a9e461dd9a17ffe
Author: Dilip Biswal <[email protected]>
Date: 2017-03-08T19:02:02Z
[SQL][MINOR] The analyzer rules are fired twice for cases AnalysisException
is raised from analyzer rules
----
---
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]
