You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2018/04/09 00:41:00 UTC
[jira] [Commented] (YARN-7892) Revisit NodeAttribute class
structure
[ https://issues.apache.org/jira/browse/YARN-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429924#comment-16429924 ]
Naganarasimha G R commented on YARN-7892:
-----------------------------------------
[~sunilg] & [~bibinchundatt],
As discussed in the meeting, have updated the Jira name and description with issues pointed out by [~bibinchundatt] & [~cheersyang]. Also have attached a WIP patch to get the early feedback and for the complete patch, planning to revisit the manager api and data structure in the manager.
> Revisit NodeAttribute class structure
> -------------------------------------
>
> Key: YARN-7892
> URL: https://issues.apache.org/jira/browse/YARN-7892
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Naganarasimha G R
> Assignee: Naganarasimha G R
> Priority: Major
> Attachments: YARN-7892-YARN-3409.001.patch, YARN-7892-YARN-3409.002.patch, YARN-7892-YARN-3409.003.WIP.patch
>
>
> In the existing structure, we had kept the type and value along with the attribute which would create confusion to the user to understand the APIs as they would not be clear as to what needs to be sent for type and value while fetching the mappings for node(s).
> As well as equals will not make sense when we compare only for prefix and name where as values for them might be different.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org