hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajat Khandelwal (JIRA)" <>
Subject [jira] [Commented] (HIVE-13415) Decouple Sessions from thrift binary transport
Date Wed, 06 Apr 2016 06:57:25 GMT


Rajat Khandelwal commented on HIVE-13415:

So my use case is an application which has a lifecycle and as a part of the lifecycle, some
queries are fired on hive server. The application has a restart capability. So the queries
fired on hive server are persisted(as operation handles) as the application stops and are
read back when the application starts up again. Now, I need those operations to not fail while
my restart is complete. I have the handles and expect handles to still be valid when I connect
to hive server again. For this, we need:

* the connection session coupling to go away
* The asynchronous queries to not fail, as discussed somewhat on HIVE-11485

As mentioned in another comment, for hive server where an operation can take a long time to
finish, recoverability is an important feature for clients to use. 

> Decouple Sessions from thrift binary transport
> ----------------------------------------------
>                 Key: HIVE-13415
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Rajat Khandelwal
>            Assignee: Rajat Khandelwal
>         Attachments: HIVE-13415.01.patch
> Current behaviour is:
> * Open a thrift binary transport
> * create a session
> * close the transport
> Then the session gets closed. Consequently, all the operations running in the session
also get killed.
> Whereas, if you open an HTTP transport, and close, the enclosing sessions are not closed.

> This seems like a bad design, having transport and sessions tightly coupled. I'd like
to fix this. 
> The issue that introduced it is [HIVE-9601|]
Relevant discussions at [here|],
and mentioned links on those comments. 
> Another thing that seems like a slightly bad design is this line of code in ThriftBinaryCLIService:
> {noformat}
> server.setServerEventHandler(serverEventHandler);
> {noformat}
> Whereas serverEventHandler is defined by the base class, with no users except one sub-class(ThriftBinaryCLIService),
violating the separation of concerns. 

This message was sent by Atlassian JIRA

View raw message