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

Eric Badger commented on YARN-7129:
-----------------------------------

I don't think -DskipDocker is the correct approach here. This gets us back to 
the exact same problem. Everyone who was building trunk just fine will now have 
to change their build approach. 

bq. 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.
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. 

bq. Using profile to generate different artifact is strongly discouraged 
practice by Maven best practice guide line.
I'm not quite sure what the validity of this best practices guide is, but one 
of the first things stated is "Good practice is to minimise the effort required 
to make a successful build." Forcing all developers to add a -D flag to their 
builds to maintain what they had before this patch is the opposite of 
minimizing effort. Only release managers or those dealing directly with this 
feature will need the docker image. Everybody that isn't using the feature 
shouldn't have to change because of that small minority. 

> 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]

Reply via email to