You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Szehon Ho (JIRA)" <ji...@apache.org> on 2018/12/12 13:12:00 UTC

[jira] [Updated] (HIVE-21033) Sudden disconnect for a session with set and SQL operation cuts off any more HiveServer2 logs

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

Szehon Ho updated HIVE-21033:
-----------------------------
    Description: 
Its a bit tricky to reproduce, but we were able to do it (unfortunately) with our custom client that did not handle closing the session on the error case.

Basically you have a session with both HiveCommandOperation and SQLOperation (set a=b; select * from foobar;).  Both will set up the session's out and err, with the SQLOperation setting it to be System.out and System.err

ref: 

> Sudden disconnect for a session with set and SQL operation cuts off any more HiveServer2 logs
> ---------------------------------------------------------------------------------------------
>
>                 Key: HIVE-21033
>                 URL: https://issues.apache.org/jira/browse/HIVE-21033
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Szehon Ho
>            Priority: Major
>
> Its a bit tricky to reproduce, but we were able to do it (unfortunately) with our custom client that did not handle closing the session on the error case.
> Basically you have a session with both HiveCommandOperation and SQLOperation (set a=b; select * from foobar;).  Both will set up the session's out and err, with the SQLOperation setting it to be System.out and System.err
> ref: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)