hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7840) Update PB for prefix support of node attributes
Date Thu, 01 Feb 2018 01:10:00 GMT

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

Sunil G commented on YARN-7840:

Thanks [~Naganarasimha] for the detailed comment. I also had a concern of map initially and
was trying to correlate it. 
{quote}If while adding the mapping we are just adding the type for the proto and no value
is mapped and hence no type attached to the Name , so  while submitting the RR what operations
are permitted  ? how to validate.
So IIUC, you were mentioning abt the validation of type vs value (cases where one is empty
and another is not etc). This will also come when its given as two different entities. After
thinking a bit, could we add this value to NodeAttributeTypeProto itself as optional param.
{quote}Assume one node sends with No value and other nodes sends it with value. validations
cannot be thought of
Similar to above, cud we think of moving value with type.


Ideally I was thinking a case where we have some more items coming in the proto and type vs
value may loose its bindness a bit, hence was thinking to correlate a bit. [~Naganarasimha]
do you think of any other good options here.

> Update PB for prefix support of node attributes
> -----------------------------------------------
>                 Key: YARN-7840
>                 URL: https://issues.apache.org/jira/browse/YARN-7840
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Weiwei Yang
>            Assignee: Naganarasimha G R
>            Priority: Blocker
>         Attachments: YARN-7840-YARN-3409.001.patch, YARN-7840-YARN-3409.002.patch, YARN-7840-YARN-3409.003.patch
> We need to support prefix (namespace) for node attributes, this will add the flexibility
to provide ability to do proper ACL, avoid naming conflicts etc.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message