[
https://issues.apache.org/jira/browse/YARN-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802394#comment-16802394
]
Eric Badger commented on YARN-7129:
-----------------------------------
bq. This is aligned with YARN-913, HDFS-7240 where patches are committed but
subtasks are on-going.
HDFS-7240 is Ozone, which had all of the subtasks committed to a feature
branch. The branch was then merged after a [\[VOTE\]
thread|http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-dev/201804.mbox/%3cdc8ce957-bcd3-4725-9e9f-3947b618c...@hortonworks.com%3E#archives]
As for YARN-913 (which is from 5 years ago), it appears that they put up and
committed the patch via YARN-2652, which is a subtask of YARN-913 (which is
exactly what I am requesting).
See [this
comment|https://issues.apache.org/jira/browse/YARN-2652?focusedCommentId=14164072&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14164072]
from YARN-2652
{quote}
This is the subset of the YARN-913 patch as 1'd by sanjay and applied to
branch-2.6, isolated for better tracking of what went in
{quote}
and [this
comment|https://issues.apache.org/jira/browse/YARN-913?focusedCommentId=14164077&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14164077]
from YARN-913
{quote}
committed the core hadoop-yarn-registry module and associated diffs; YARN-2562
contains the exact patch applied to branch-2.6 & branch-2; trunk gets the same
with the POM updated to version 3.0.0
{quote}
Creating a subtask and adding this patch to it will take less than 5 minutes,
fixes the release notes problem, and allows for the JIRA where the patch was
committed to actually be closed. All conversation will be preserved on this
JIRA and this JIRA itself can be linked to the subtask. A simple comment in the
summary of the subtask could refer back to this JIRA for reference pointing
everyone back here to read the discussion.
I think that moving this patch into a subtask is a very reasonable request and
don't understand the pushback.
> Application Catalog for YARN applications
> -----------------------------------------
>
> Key: YARN-7129
> URL: https://issues.apache.org/jira/browse/YARN-7129
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: applications
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Attachments: YARN Appstore.pdf, YARN-7129.001.patch,
> YARN-7129.002.patch, YARN-7129.003.patch, YARN-7129.004.patch,
> YARN-7129.005.patch, YARN-7129.006.patch, YARN-7129.007.patch,
> YARN-7129.008.patch, YARN-7129.009.patch, YARN-7129.010.patch,
> YARN-7129.011.patch, YARN-7129.012.patch, YARN-7129.013.patch,
> YARN-7129.014.patch, YARN-7129.015.patch, YARN-7129.016.patch,
> YARN-7129.017.patch, YARN-7129.018.patch, YARN-7129.019.patch,
> YARN-7129.020.patch, YARN-7129.021.patch, YARN-7129.022.patch,
> YARN-7129.023.patch, YARN-7129.024.patch, YARN-7129.025.patch,
> YARN-7129.026.patch, YARN-7129.027.patch, YARN-7129.028.patch,
> YARN-7129.029.patch, YARN-7129.030.patch, YARN-7129.031.patch,
> YARN-7129.032.patch, YARN-7129.033.patch, YARN-7129.034.patch,
> YARN-7129.035.patch
>
>
> YARN native services provides web services API to improve usability of
> application deployment on Hadoop using collection of docker images. It would
> be nice to have an application catalog system which provides an editorial and
> search interface for YARN applications. This improves usability of YARN for
> manage the life cycle of applications.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
