Skip to content

[SPARK-18867] [SQL] Throw cause if IsolatedClientLoad can't create cl… - #16285

Closed
jojochuang wants to merge 1 commit into
apache:masterfrom
jojochuang:master
Closed

[SPARK-18867] [SQL] Throw cause if IsolatedClientLoad can't create cl…#16285
jojochuang wants to merge 1 commit into
apache:masterfrom
jojochuang:master

Conversation

@jojochuang

Copy link
Copy Markdown

What changes were proposed in this pull request?

If IsolatedClientLoader can't instantiate a class object, it throws InvocationTargetException. But the caller doesn't need to know this exception. Instead, it should throw the exception that causes the InvocationTargetException, so that the caller may be able to handle it.

How was this patch tested?

(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Please review http://spark.apache.org/contributing.html before opening a pull request.

…ient

@AmplabJenkins

Copy link
Copy Markdown

Can one of the admins verify this patch?

@rxin

rxin commented Dec 15, 2016

Copy link
Copy Markdown
Contributor

Is it ever possible cause is null?

@jojochuang

Copy link
Copy Markdown
Author

@rxin

rxin commented Dec 16, 2016

Copy link
Copy Markdown
Contributor

Thanks for looking into it. In that case, maybe we should just keep the thing as is and don't change it?

@HyukjinKwon

Copy link
Copy Markdown
Member

Hi @jojochuang, is it still active? If so, I think we should address this comment ^.

@HyukjinKwonHyukjinKwon mentioned this pull request May 17, 2017
zifeif2 pushed a commit to zifeif2/spark that referenced this pull request Nov 22, 2025
## What changes were proposed in this pull request?
This PR proposes to close PRs ...
- inactive to the review comments more than a month
- WIP and inactive more than a month
- with Jenkins build failure but inactive more than a month
- suggested to be closed and no comment against that
- obviously looking inappropriate (e.g., Branch 0.5)
To make sure, I left a comment for each PR about a week ago and I could not have a response back from the author in these PRs below:
Closesapache#11129Closesapache#12085Closesapache#12162Closesapache#12419Closesapache#12420Closesapache#12491Closesapache#13762Closesapache#13837Closesapache#13851Closesapache#13881Closesapache#13891Closesapache#13959Closesapache#14091Closesapache#14481Closesapache#14547Closesapache#14557Closesapache#14686Closesapache#15594Closesapache#15652Closesapache#15850Closesapache#15914Closesapache#15918Closesapache#16285Closesapache#16389Closesapache#16652Closesapache#16743Closesapache#16893Closesapache#16975Closesapache#17001Closesapache#17088Closesapache#17119Closesapache#17272Closesapache#17971
Added:
Closesapache#17778Closesapache#17303Closesapache#17872
## How was this patch tested?
N/A
Author: hyukjinkwon <gurwls223@gmail.com>
Closesapache#18017 from HyukjinKwon/close-inactive-prs.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@jojochuang@AmplabJenkins@rxin@HyukjinKwon