[
https://issues.apache.org/jira/browse/IMPALA-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong reassigned IMPALA-3351:
-------------------------------------
Assignee: (was: Syed A. Hashmi)
> Improve error reporting for JDBC clients
> ----------------------------------------
>
> Key: IMPALA-3351
> URL: https://issues.apache.org/jira/browse/IMPALA-3351
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Affects Versions: Impala 2.0
> Reporter: Xiaomin Zhang
> Priority: Minor
> Labels: jdbc
>
> For JDBC client such as beeline:
> beeline> !connect
> jdbc:hive2://quickstart.cloudera:21050/;principal=impala/quickstart.cloudera@CLOUDERA
> For queries such as "SELECT * FROM CUSTOMER", when CUSTOMER does not exist, I
> get below error:
> Error: AnalysisException: Could not resolve table reference: 'customer'
> (state=HY000,code=0)
> However, for queries such as "SELECT * FROM CUSTOMERS", when this table is
> using non-supported definition, I will get below error message:
> Error: Invalid query handle (state=HY000,code=0)
> There's no detailed and useful information returned. The only way to
> troubleshooting this query is to look into the impalad log, I can see errors
> like:
> Error from query ca4ae093852af48b:a7d9cec9fae3ab4: File
> hdfs://quickstart.cloudera:8020/user/hive/warehouse/customers/customers has
> invalid file metadata at file offset 2183. Error = couldn't deserialize
> thrift msg:
> TProtocolException: Invalid data
> So this looks that JDBC client cannot get detailed SQL exception when the
> underlining error happens on fragments.
> Is it possible to also bring those runtime error information to JDBC clients?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
