hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantinos Karanasos (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6593) [API] Introduce Placement Constraint object
Date Tue, 23 May 2017 22:57:04 GMT

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

Konstantinos Karanasos commented on YARN-6593:
----------------------------------------------

Let's avoid bold in the JIRAs without a reason guys :)
We have a different approach in mind, but that's OK. Let's try to see the other person's point
of view, it will help the end users too :)

The difference is minor; we have a POC that does not require differentiating constraint classes,
so that will break the symmetry from the other side, but that's OK, if it will help us converge.
I do find it a pity to add unnecessary subclasses, but I want to move forward.

So, [~leftnoteasy], you would prefer different subclasses for each type of constraint. Therefore,
we will have one for the target, one for the cardinality, and one that combines both, right?

> [API] Introduce Placement Constraint object
> -------------------------------------------
>
>                 Key: YARN-6593
>                 URL: https://issues.apache.org/jira/browse/YARN-6593
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Konstantinos Karanasos
>            Assignee: Konstantinos Karanasos
>         Attachments: YARN-6593.001.patch, YARN-6593.002.patch
>
>
> This JIRA introduces an object for defining placement constraints.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


Mime
View raw message