[
https://issues.apache.org/jira/browse/YARN-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791978#comment-16791978
]
Eric Yang commented on YARN-7129:
---------------------------------
[~ebadger] {quote}No. This is exactly what you had in the patch that was
committed that broke my build environment. The whole point here is that I
shouldn't need a workaround to maintain my working build environment.{quote}
Base on this philosophy, the project should never change the build environment.
Project should never include new capabilities because new change will break
the build requirement. We must call Hadoop 0.1 release final using ant build
because the build environment should never change.
{quote}Good practice is to minimise the effort required to make a successful
build.{quote}
The best practice is not emphasize minimize effort for someone who doesn't want
a complete build, the end of the same paragraph in maven profile best practice
stated:
{quote}A maintainer coming to the project will not immediately know that
profile wibblewibble has to be activated for the build to succeed. Don't make
her waste time finding it out.{quote}
The emphasize is on the maintainer at end of the paragraph, which covers
release manager and developers to make a usable build. Many people have
devoted their time to make Hadoop easier to build. If BUILD.txt instruction is
followed, this would not have been an issue. We have given our best effort to
make this project as effort less to build as possible, and the only requirement
is to build the project with the docker environment for ease of setup. For
experienced developers, they may choose to build a subset of the project. This
can be done with good knowledge of the tool chain. Most people acquired
-DskipTests skill very quickly. I think the same can be applied to
-DskipShade, -DskipDocker features. With the right maven skills, fast building
of subset is possible without requiring to revert patches to acquire this
knowledge.
In the five different options of avoiding docker builds, -pl and -DskipDocker
are maven proper. They are features that comes with maven tool chain. Other
three options are also Hadoop proper by meeting the requirement of having
access to docker or completely absent. If you insist on developer should never
change build environment, then I would suggest to continue on the discussion
thread in Hadoop dev mailing lists to resolve whether we should build docker
image inline with community consensus. This issue is not the right place for
that discussion. Though this issue depends on the outcome of the community
consensus.
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
