[
https://issues.apache.org/jira/browse/DRILL-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539309#comment-14539309
]
Daniel Barclay (Drill) edited comment on DRILL-3020 at 5/12/15 6:02 AM:
------------------------------------------------------------------------
Commit message:
DRILL-3020: Copy cause exception's message to thrown SQLException's message.
Changed SQLException construction to set SQLException's message to the cause
exception's toString().
Also:
- Narrowed one SQLException to SQLNonTransientConnectionException (not other
two, since unclear whether transient, non-transient, or varied).
- Clarified/simplified exception messages.
- Fixed message typo.
was (Author: dsbos):
DRILL-3020: Copy cause exception's message to thrown SQLException's message.
Changed SQLException construction to set SQLException's message to the cause
exception's toString().
Also:
- Narrowed one SQLException to SQLNonTransientConnectionException (not other
two, since unclear whether transient, non-transient, or varied).
- Clarified/simplified exception messages.
- Fixed message typo.
> Some exception message text not displayed in SQLLine, etc.; copy to thrown
> SQLException's message
> -------------------------------------------------------------------------------------------------
>
> Key: DRILL-3020
> URL: https://issues.apache.org/jira/browse/DRILL-3020
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - JDBC
> Reporter: Daniel Barclay (Drill)
> Assignee: Daniel Barclay (Drill)
> Attachments: DRILL-3020.1.patch.txt
>
>
> In the JDBC driver, for some SQLException thrown to wrap underlying
> exceptions, the thrown SQLException's message text does not include any
> information from the underlying exception.
> The means that the underlying message text is less likely to be visible to
> the end user. (For example, SQLLine display's a SQLException's message text,
> but not normally its stack track or the message text of chained exceptions.)
> (Note that does not apply to UserExceptions from the server; that case is
> already handled.)
>
> For those cases, the JDBC driver should copy more information into the
> top-level SQLException's message text (e.g., copy the message text of the
> next chained exception, as it already does for UserExceptions.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
