hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17455) External LLAP client: connection to HS2 should be kept open until explicitly closed
Date Wed, 06 Sep 2017 18:40:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-17455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155861#comment-16155861
] 

Sergey Shelukhin commented on HIVE-17455:
-----------------------------------------

Hm... this seems very error prone, esp. if users don't even set the handle in the jobconf.
Perhaps some method (init of some sort? or getSplits itself, since it's called explicitly)
should return a closeable encapsulating the handle, so that it could be closed via normal
means?

> External LLAP client: connection to HS2 should be kept open until explicitly closed
> -----------------------------------------------------------------------------------
>
>                 Key: HIVE-17455
>                 URL: https://issues.apache.org/jira/browse/HIVE-17455
>             Project: Hive
>          Issue Type: Sub-task
>          Components: llap
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>         Attachments: HIVE-17455.1.patch, HIVE-17455.2.patch
>
>
> In the case that a complex query (aggregation/join) is passed to external LLAP client,
the query result is first saved as a Hive temp table before being read by LLAP to client.
Currently the HS2 connection used to fetch the LLAP splits is closed right after the splits
are fetched, which means the temp table is gone by the time LLAP tries to read it.
> Try to keep the connection open so that the table is still around when LLAP tries to
read it. Add close methods which can be used to close the connection when the client is done
with the query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message