[ 
https://issues.apache.org/jira/browse/HIVE-26345?focusedWorklogId=783228&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-783228
 ]

ASF GitHub Bot logged work on HIVE-26345:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Jun/22 07:08
            Start Date: 21/Jun/22 07:08
    Worklog Time Spent: 10m 
      Work Description: zhangbutao commented on PR #3393:
URL: https://github.com/apache/hive/pull/3393#issuecomment-1161346902

   @belugabehr @pvary @zabetak wdyt? Thank you.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 783228)
    Time Spent: 20m  (was: 10m)

> SQLOperation class output real exception message to jdbc client
> ---------------------------------------------------------------
>
>                 Key: HIVE-26345
>                 URL: https://issues.apache.org/jira/browse/HIVE-26345
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>    Affects Versions: 4.0.0-alpha-2
>            Reporter: zhangbutao
>            Assignee: zhangbutao
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Beeline client may can not get real exception from _*SQLOperation class*_ and 
> user may don't how to fix query based on client exception massage.
> Step to repro:
> {code:java}
> set hive.support.concurrency=false;
> set hive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager;
> create table testacid(id int) stored as orc 
> tblproperties('transactional'='true');{code}
> Beeline console output exception:
> {code:java}
> Error: Error running query (state=,code=0) {code}
>  
> However, Hive3 beeline can output readable exception information:
> {code:java}
> Error: Error while compiling statement: FAILED: RuntimeException [Error 
> 10264]: To use DbTxnManager you must set hive.support.concurrency=true 
> (state=42000,code=10264) {code}
>  
> This change was introduced by HIVE-23124, i think we should fix this to 
> output real exception to prompt users to amend the query.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to