GitHub user liancheng opened a pull request:

    https://github.com/apache/spark/pull/11677

    [SQL] Bring back stack trace of AnalysisException thrown from 
QueryExecution.assertAnalyzed

    ## What changes were proposed in this pull request?
    
    PR #11443 added an extra `plan: Option[LogicalPlan]` argument to 
`AnalysisException` and attached partially analyzed plan to thrown 
`AnalysisException` in `QueryExecution.assertAnalyzed()`.  However, the 
original stack trace wasn't properly inherited.  This PR fixes this issue by 
inheriting the stack trace.
    
    ## How was this patch tested?
    
    A test case is added to verify that the first entry of `AnalysisException` 
stack trace isn't from `QueryExecution`.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/liancheng/spark analysis-exception-stacktrace

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/11677.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 #11677
    
----
commit 776d3aa23adcef0eff3a36ebe04f6e4887a7bb28
Author: Cheng Lian <l...@databricks.com>
Date:   2016-03-12T10:47:09Z

    Inherits AnalysisException stack trace in assertAnalyzed

commit 00f299ba0462af9fc9448295c7856e2dc2dbb8b2
Author: Cheng Lian <l...@databricks.com>
Date:   2016-03-12T11:08:31Z

    Test

----


---
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

Reply via email to