GitHub user kunalkhamar opened a pull request:
https://github.com/apache/spark/pull/17486
[SPARK-20164][SQL][WIP] AnalysisException not tolerant of null query plan.
## What changes were proposed in this pull request?
When someone throws an AnalysisException with a null query plan (which
ideally no one should), getMessage is not tolerant of this and throws a null
pointer exception, leading to loss of information about original exception.
Fix is to add a null check in getMessage.
## How was this patch tested?
- Unit test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kunalkhamar/spark spark-20164
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/17486.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 #17486
----
commit e3c1970a3a715e8e8042384bb81bcc86730d6d81
Author: Kunal Khamar <kkha...@outlook.com>
Date: 2017-03-30T21:11:58Z
Add null check to AnalysisException.
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
