[
https://issues.apache.org/jira/browse/HADOOP-15821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639643#comment-16639643
]
Steve Loughran commented on HADOOP-15821:
-----------------------------------------
it was always intended to be moveable; everything, eventually, needs a lookup
mechanism. Hence the packaging.
* anything which has an explicit dependency on the yarn-registry artifact isn't
going to build any more. It'll need a stub POM
* the imports are being reordered a lot, and not into the "recommended" hadoop
order either. Can you leave them as close to the originals as possible, as
import reorderings always make cherry picking such a PITA. (I know, it's a
move, but still)
* moving to loading configuration over YarnConfiguration means that
yarn-site.xml isn't going to get picked up. If that's where any deployment
configures the registry, things will break. I propose using some reflection
game to instantiate a YarnConfiguration instance if it's on the classpath.
* yes, move the .tla file; probably needs editing & a rebuild of the PDF too. I
should help there (maybe: make editing this a followup & assign to me, unless
you want to learn TLA+).
* Why the changes to RegistryDNS?
> 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,
> HADOOP-15821.002.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]
