[
https://issues.apache.org/jira/browse/HIVE-7553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093251#comment-14093251
]
Brock Noland commented on HIVE-7553:
------------------------------------
Hi [~Ferd],
Thank you very much for creating the design document! Please do not worry about
uploading to the wiki today, we'll do that once we've iterated on the design.
Could you add a few diagrams of user sessions and classloaders? I think that
would help clarify things.
bq. When finding a class, it will check the parent class loader first
I believe that something similar has been in for servlet containers in the
past. Can you add an overview what was done and how it works to Class loader
Features?
bq. . HiveConf will hold the custom class loader.
What is the scope of the HiveConf object without a user session? When is it
created and destroyed? Any user can execute add jar, will each user have their
own instance of the class loader.
> 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)
