[
https://issues.apache.org/jira/browse/HADOOP-10376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028731#comment-14028731
]
Chris Li commented on HADOOP-10376:
-----------------------------------
Thanks for reviewing!
I think the next step is to start moving other refreshProtos towards the
generic proto, marking things as deprecated along the way. I'll start with
RefreshCallQueue since it's the newest. HADOOP-10685 to track
> 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
> Fix For: 3.0.0, 2.5.0
>
> Attachments: HADOOP-10376.patch, HADOOP-10376.patch,
> HADOOP-10376.patch, HADOOP-10376.patch, 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)
