[
https://issues.apache.org/jira/browse/HADOOP-10376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Li updated HADOOP-10376:
------------------------------
Attachment: HADOOP-10376.patch
Hi [~arpitagarwal], sounds good. I went ahead and uploaded a patch.
Most of it is pretty typical stuff for adding a new protocol (which shows how
painful it is today), the interesting parts are the 3 new files:
RefreshRegistry, RefreshHandler, RefreshResponse.
A useful new capability is being able to send text and exit status to the user
on success (today you can either return 0 and have no text, or throw an
exception with a message and return -1)
Authorization is coarse in this patch: users can be opted in or out of
refreshing any of the registered refresh handlers. Future versions would allow
more fine permissions.
> Refactor refresh*Protocols into a single generic refreshConfigProtocol
> ----------------------------------------------------------------------
>
> Key: HADOOP-10376
> URL: https://issues.apache.org/jira/browse/HADOOP-10376
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Chris Li
> Assignee: Chris Li
> Priority: Minor
> Attachments: HADOOP-10376.patch, RefreshFrameworkProposal.pdf
>
>
> See https://issues.apache.org/jira/browse/HADOOP-10285
> There are starting to be too many refresh*Protocols We can refactor them to
> use a single protocol with a variable payload to choose what to do.
> Thereafter, we can return an indication of success or failure.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
