[
https://issues.apache.org/jira/browse/HIVE-7553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14114245#comment-14114245
]
Lefty Leverenz commented on HIVE-7553:
--------------------------------------
Doc question (also posted on the review board): one parameter description says
"renewed by executing reload command" but the other adds "refresh" to its
default values. Which is correct, reload or refresh?
Answering myself: The first patch had "refresh" for both, but patch 1 changes
"hive.refresh.aux.jars.path" to "hive.reloadable.aux.jars.path" so I guess my
review board question was backwards -- reload is correct and you need to change
"refresh" to "reload" in the default values for hive.security.command.whitelist.
Otherwise the parameters are good to go. Thanks for the fixes, [~Ferd].
> 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.1.patch, HIVE-7553.patch, 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)
