drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Barclay (Drill) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-2932) Error text reported via System.out.println rather than thrown SQLException's message
Date Mon, 04 May 2015 20:35:06 GMT

     [ https://issues.apache.org/jira/browse/DRILL-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Barclay (Drill) updated DRILL-2932:
------------------------------------------
    Summary: Error text reported via System.out.println rather than thrown SQLException's
message  (was: Errors reported through System.out.println, and text not in thrown SQLException
message)

> Error text reported via System.out.println rather than thrown SQLException's message
> ------------------------------------------------------------------------------------
>
>                 Key: DRILL-2932
>                 URL: https://issues.apache.org/jira/browse/DRILL-2932
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>            Reporter: Daniel Barclay (Drill)
>            Assignee: Daniel Barclay (Drill)
>            Priority: Critical
>
> There is a call to System.out.println(...) in DrillResultSetImpl.ResultListener.submissionFailed(...):
>   System.out.println("Query failed: " + ex.getMessage());
> (That submissionFailed(...) is part of the implementation of Statement.execute...(...)
methods and ResultSet.)
> In SQLLine, this causes the exception message, which currently doesn't show up otherwise
in SQLLine, to show up when running SQLLine interactively.
> However, writing that to System.out. is completely inappropriate. 
> JDBC specifies that implementations throw SQLExceptions to report errors\--implementations
should not be unilaterally be deciding to write to stdout\--or stderr.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message