[
https://issues.apache.org/jira/browse/HADOOP-15821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638974#comment-16638974
]
Íñigo Goiri commented on HADOOP-15821:
--------------------------------------
[^HADOOP-15821.000.patch] includes a first pass to prove that there are no real
dependencies with YARN.
There are a few open issues here:
* Had to change YarnConfiguration, YarnUncaughtExceptionHandler and
YarnRuntimeException.
* Backwards compatibility: I'm not sure if this is public, should we create
bindings for backwards compatibility?
* Documentation: currently is in the YARN section and it could be moved here.
It would need some re-wording though.
* References to YARN: in the current patch, there are a couple references to
YARN, should we move them?
** PersistencePolicies
** YarnRegistryAttributes
** SelectByYarnPersistence
** yarnregistry.tla
[[email protected]], [~billie.rinaldi], [~eyang], you guys commented in
HADOOP-15774 about this possibility.
Any thoughts?
> 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
> Priority: Major
> Attachments: HADOOP-15821.000.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]
