Konstantinos Karanasos commented on YARN-7921:

Hi [~cheersyang],

.bq what I was trying to do with this task is to implement 2). Which will be 
done by implementing {{AbstractConstraint#toString}} methods.

Agreed. I was thinking that we could instead create a visitor, so that we can 
have different toString representations and we can also take advantage of the 
transformations more easily (for example you can first call a transformation 
and then do the string representation). But I guess we can start by just 
overriding the toString method.

> Transform a PlacementConstraint to a string expression
> ------------------------------------------------------
>                 Key: YARN-7921
>                 URL: https://issues.apache.org/jira/browse/YARN-7921
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>            Priority: Major
> Purpose:
> Let placement constraint viewable on UI or log, e.g print app placement 
> constraint in RM app page. Help user to use constraints and analysis 
> placement issues easier.
> Propose:
> Like what was added for DS, toString is a reversed process of 
> {{PlacementConstraintParser}} that transforms a PlacementConstraint to a 
> string, using same syntax. E.g
> {code}
> AbstractConstraint constraintExpr = targetIn(NODE, allocationTag("hbase-m"));
> constraint.toString();
> // This prints: IN,NODE,hbase-m
> {code}

This message was sent by Atlassian JIRA

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

Reply via email to