[
https://issues.apache.org/jira/browse/HIVE-7553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089396#comment-14089396
]
Brock Noland commented on HIVE-7553:
------------------------------------
Hi [~Ferd],
Thank you so much for looking into this!! I think you have a good direction on
some of the possible solutions. I do think this is a very big item with many
different aspects.
Would you be interested in creating a design document on this? There are many
examples out there: https://cwiki.apache.org/confluence/display/Hive/DesignDocs
e.g: https://cwiki.apache.org/confluence/display/Hive/Theta+Join
If you create a design doc, I think the big aspect of this design doc would be
evaluate all the pros/cons of each possible solution.
Thank you again for looking at this!!
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
>
> 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)
