[
https://issues.apache.org/jira/browse/YARN-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791009#comment-16791009
]
Eric Yang commented on YARN-7129:
---------------------------------
[~ebadger] {quote}I could make the same argument about native code. Not
everyone needs the native code in their builds. If we added that in by default
then the build time would slow down a lot for no real reason. Release managers
know that they should build the native code and so they do. In the same way,
they can enable this docker profile to the build when they are doing a
release.{quote}
Native profile is breaking the maven best practice that generate architecture
dependent binary. Several years ago, there were discussions on this but no
body bother to make it right. Hadoop still doesn't have a good release process
to include multiple architecture binaries in maven repository. At least we
don't upload the native binary to maven repository for Hadoop to cause more
troubles. Hadoop build requires protoc 2.6. If OS updated to protoc 3.x, user
have to fix their environment. Changes are bounded to happen, and hopefully as
non-disruptive as possible. I have intention to make this as smooth as
possible.
Maybe calling a vote on this change would be provide better experience for
developer to adopt to change? It's too late to rationalize this, and I
apologize for inconvenience occurred. The key point is how to move forward.
Now, Hadoop build process intended to introduce inline docker build using
signed jar files. What change can improve the build procedure for better
experience for dev?
> 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]
