[
https://issues.apache.org/jira/browse/YARN-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535302#comment-15535302
]
Jian He commented on YARN-5610:
-------------------------------
bq. No, I meant that our REST API yaml document specifies the expected and
supported format of lifetime to be like "30mins, 10hours, 5days"
Then, I feel the REST API could be long type. The caller code could define the
user-friendly string format and convert it to the long type. I feel his is more
flexible for programatic use, otherwise we need to define a proper string time
schema and user code needs to implement the logic about how to convert a long
value to the string type.
> Initial code for native services REST API
> -----------------------------------------
>
> Key: YARN-5610
> URL: https://issues.apache.org/jira/browse/YARN-5610
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Gour Saha
> Assignee: Gour Saha
> Fix For: yarn-native-services
>
> Attachments: YARN-4793-yarn-native-services.001.patch,
> YARN-5610-yarn-native-services.002.patch,
> YARN-5610-yarn-native-services.003.patch
>
>
> This task will be used to submit and review patches for the initial code drop
> for the native services REST API
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
