hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7129) Application Catalog for YARN applications
Date Tue, 12 Mar 2019 20:04:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790965#comment-16790965

Eric Yang commented on YARN-7129:

[~ebadger] [~eepayne] [~vinodkv], I recognize the importance of not breaking developer's environment
unless there is a good reason.  How about we introduce -DskipDocker in the same tune to skip
shaded jars for avoiding certain features?

This is similar to shaded jar files that the build process happens by default in order to
guarantee recursive dependent artifacts can all be signed.  Inline build process is the only
proper solution to ensure the build is reproducible and properly signed.  If we have intend
to ensure that we can release docker image with signed hadoop jar file embedded in the docker
image, and then sign the docker image for release.  I think docker build should be on by default
with option to turn off.

Using profile to generate different artifact is strongly discouraged practice by [Maven best
practice guide line|https://dzone.com/articles/maven-profile-best-practices].  There are important
merits in the guideline to avoid build/release problems for maven repository.  This is the
reason that I did not use profile to activate docker build profile.  Let me know your thoughts
and there might be better way to resolve this issue than revert.  Thanks

> 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
>             Fix For: 3.3.0
>         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 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message