[
https://issues.apache.org/jira/browse/YARN-7186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163589#comment-16163589
]
Gour Saha commented on YARN-7186:
---------------------------------
bq. Yes, it is not very convenient having the name specified in the json,
because it makes it harder to reuse the json. Adding back an optional service
name for the create command that would override the name specified in the json
would be a reasonable way to mitigate this issue.
+1 for making service-name optional and override name in the json. We need to
explicitly mention this in the cmd line description for \[service-name\] though.
bq. Naming it --example would be okay.
+1 for this as well. Is the path where the example jsons will be available, a
standard path? Does an env need to be exposed so that this path can be
overridden?
> Add examples in yarn-service
> -----------------------------
>
> Key: YARN-7186
> URL: https://issues.apache.org/jira/browse/YARN-7186
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jian He
> Assignee: Jian He
> Attachments: YARN-7186.yarn-native-services.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
