GitHub user bomeng opened a pull request:
https://github.com/apache/spark/pull/12314
[SPARK-14414] [SQL] improve the error message class hierarchy
## What changes were proposed in this pull request?
Before we are using AnalysisException, ParseException,
NoSuchFunctionException etc when a parsing error encounters. I am trying to
make it consistent and also minimum code impact to the current implementation
by changing the class hierarchy.
1. NoSuchItemException is removed, it is an abstract class and it just
simply takes a message string.
2. NoSuchDatabaseException, NoSuchTableException, NoSuchPartitionException
and NoSuchFunctionException now extends AnalysisException, as well as
ParseException, they are all under AnalysisException umbrella, but you can also
determine how to use them in a granular way.
## How was this patch tested?
The existing test cases should cover this patch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bomeng/spark SPARK-14414
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/12314.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 #12314
----
commit ee3c4f72d83cb00d3debefde96cfc050321eddb2
Author: bomeng <[email protected]>
Date: 2016-04-12T00:27:34Z
improve the error message class hierarchy
----
---
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]
