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

Hudson commented on YARN-7100:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13193 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13193/])
YARN-7100. Added JsonIgnore annotation to Resource#getMemoryMB. (jianhe: rev 
59fe98cd50b34eb75c5f522aa6f3a53bd650b15e)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/api/records/Resource.java


> YARN service api can not reuse json file serialized in hdfs
> -----------------------------------------------------------
>
>                 Key: YARN-7100
>                 URL: https://issues.apache.org/jira/browse/YARN-7100
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn-native-services
>    Affects Versions: 3.0.0-beta1
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: yarn-native-services
>
>         Attachments: YARN-7100.001.patch, 
> YARN-7100.002.yarn-native-services.patch, 
> YARN-7100.003.yarn-native-services.patch, 
> YARN-7100.004.yarn-native-services.patch
>
>
> org.apache.hadoop.yarn.service.api.records.Resource has a new method 
> introduced in YARN-6903 for casting memory from string to long value.  
> However, the method name getMemoryMB introduces new output in json that looks 
> like this:
> {code}
>     "resource" : {
>       "uri" : null,
>       "profile" : null,
>       "cpus" : 1,
>       "memory" : "2048",
>       "memory_mb" : 2048
>     },
> {code}
> This prevents the file to be resubmitted to services api because memory_mb 
> property is unknown to the REST API.  It may be better to rename getMemoryMB 
> method to calcMemoryMB to avoid the method to be serialized unintentionally.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to