[
https://issues.apache.org/jira/browse/DRILL-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531356#comment-14531356
]
Jason Altekruse commented on DRILL-2973:
----------------------------------------
Just talked to Daniel, he had deleted the system.out call in the first patch
assuming it was old debugging code. Considering it was in the jdbc driver
itself, it seems like a reasonable assumption that we should not have been
relying on the jdb driver sharing a common system out with the jdbc application
to report error messages.
He does have a change as described by sudheesh that should fix this and he is
rebasing the patch and confirming that it fixes this issue.
> Error messages not showing up in sqlline
> ----------------------------------------
>
> Key: DRILL-2973
> URL: https://issues.apache.org/jira/browse/DRILL-2973
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Reporter: Rahul Challapalli
> Assignee: Daniel Barclay (Drill)
> Priority: Blocker
> Labels: error_message_must_fix
> Fix For: 1.0.0
>
> Attachments: error.log
>
>
> git.commit.id.abbrev=3b19076
> This could be a regression. I am not seeing any error messages. Below are
> some of the cases
> {code}
> 0: jdbc:drill:schema=dfs_eea> select * from sdkjgfhsjkdgf;
> Error: exception while executing query: Failure while executing query.
> (state=,code=0)
> {code}
> The logs have the right messages. For some reason they are not being
> propagated to sqlline. I attached the error log.
> {code}
> 0: jdbc:drill:schema=dfs_eea> this is crap;
> Error: exception while executing query: Failure while executing query.
> (state=,code=0)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
