Skip to content

[ZEPPELIN-1116]send out more exception msg#1379

Closed
passionke wants to merge 3 commits intoapache:masterfrom
passionke:passionke-jdbc-better-errortips
Closed

[ZEPPELIN-1116]send out more exception msg#1379
passionke wants to merge 3 commits intoapache:masterfrom
passionke:passionke-jdbc-better-errortips

Conversation

@passionke
Copy link
Contributor

What is this PR for?

better jdbc error msg make people know the true error clearly.

What type of PR is it?

Improvement

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-1116

How should this be tested?

Outline the steps to test the PR here.

Screenshots (if appropriate)

image

Questions:

  • Does the licenses files need update? no
  • Is there breaking changes for older versions? no
  • Does this needs documentation? no

in sql case, the real error exception stack is hide in e.getCause.getCause. use printStackTrace to receive all the stack trace make people know true reason.

in sql case, the real error exception stack is hide in e.getCause.getCause. use printStackTrace to receive all the stack trace make people know true reason.
@jongyoul
Copy link
Member

LGTM

@jongyoul
Copy link
Member

I have a question. Is it OK not to close baos explicitly in multi user environments?

@passionke
Copy link
Contributor Author

thanks your advice, It seems that the memory-based ByteArrayOutputStream do not need a close() method to release resources.

Here is an answer at http://stackoverflow.com/questions/2330569/closing-a-bytearrayoutputstream-has-no-effect

@jongyoul
Copy link
Member

jongyoul commented Sep 6, 2016

@passionke Sorry for the late reply. Thanks for the comment. LGTM.

@asfgit asfgit closed this in 09870cc Sep 6, 2016
@jongyoul
Copy link
Member

jongyoul commented Sep 6, 2016

@passionke Can you tell me your jira id?

@jongyoul
Copy link
Member

jongyoul commented Sep 6, 2016

I found you by your email.

@passionke passionke deleted the passionke-jdbc-better-errortips branch September 8, 2016 06:33
Sign up for free to 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.

2 participants