[
https://issues.apache.org/jira/browse/HADOOP-15821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638990#comment-16638990
]
Eric Yang commented on HADOOP-15821:
------------------------------------
{quote}Had to change YarnConfiguration, YarnUncaughtExceptionHandler and
YarnRuntimeException.{quote}
The class name change is not a problem. No regression from user point of view.
{quote}Backwards compatibility: I'm not sure if this is public, should we
create bindings for backwards compatibility?{quote}
Configuration keys are using hadoop.registry.*, it is probably ok to have them
move to core-default.xml without having to do much.
{quote}References to YARN: in the current patch, there are a couple references
to YARN, should we move them?{quote}
I am in favor of s/YARN/Hadoop/ for the remaining references.
> Move Hadoop YARN Registry to Hadoop Registry
> --------------------------------------------
>
> Key: HADOOP-15821
> URL: https://issues.apache.org/jira/browse/HADOOP-15821
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Íñigo Goiri
> Assignee: Íñigo Goiri
> Priority: Major
> Attachments: HADOOP-15821.000.patch, HADOOP-15821.001.patch
>
>
> Currently, Hadoop YARN Registry is in YARN. However, this can be used by
> other parts of the project (e.g., HDFS). In addition, it does not have any
> real dependency to YARN.
> We should move it into commons and make it Hadoop Registry.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
