[
https://issues.apache.org/jira/browse/YARN-6593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014940#comment-16014940
]
Wangda Tan commented on YARN-6593:
----------------------------------
Thanks [~kkaranasos] for your explanations.
Yeah I think you're correct, for the current PB, we cannot do extend easily on
the PB side. However we can still improve Java API:
For example, PlacementConstraints: Inside the PlacementConstraintProto, we can
add CompoundType / Children / DelayCriteria / Everything in the
SimplePlacementConstraintProto. And a field to indicate if it is a
CompoundConstraint / (Simple)TargetConstraint / (Simple)CardinalityConstraint.
With this, we can at least make Java API can be very clear, same as what we
defined in design doc, and Java side takes responsibility to translate
user-facing API and PB. Please share your thoughts, +[~asuresh].
bq. My question was more about how do we validate constraints
+1 to have a validator in common layer so client side can do validation as
well. I think validation has two phases: 1) Client side static validation 2)
Server side dynamic validation, #2 will look at cluster state and check things
like if constraints added to cluster or not, etc.
> [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
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
