hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brock Noland (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-7553) avoid the scheduling maintenance window for every jar change
Date Tue, 12 Aug 2014 23:02:12 GMT

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

Brock Noland commented on HIVE-7553:
------------------------------------

Hi [~Ferd],

Thank you very much for uploading the POC code!!

I think with this approach, we'll have to be sure we don't hold on to references to the class
as that will keep the class and classloader around, causing a memory leak. As such, I think
we'll have to change some of the work done in HIVE-6262 so we don't keep references around.


Additionally, I think we'll want to do something similar to the UDF case when we load input
and output formats, storage handlers, and serdes as these can all be specified as custom classes
on the command. 

What are your thoughts on these topics?

Cheers!
Brock

> avoid the scheduling maintenance window for every jar change
> ------------------------------------------------------------
>
>                 Key: HIVE-7553
>                 URL: https://issues.apache.org/jira/browse/HIVE-7553
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Ferdinand Xu
>            Assignee: Ferdinand Xu
>         Attachments: HIVE-7553.pdf
>
>
> When user needs to refresh existing or add a new jar to HS2, it needs to restart it.
As HS2 is service exposed to clients, this requires scheduling maintenance window for every
jar change. It would be great if we could avoid that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message