Wangda Tan commented on YARN-6594:


I just checked the latest patch, beyond the stable api below, patch looks good. 

174         @Public
175         @Stable
176         public SchedulingRequest build() {
177           return schedulingRequest;
178         }

For rest of the debates, I suggest to move it to future tasks and not block the 
feature development, what do you guys think?

> [API] Introduce SchedulingRequest object
> ----------------------------------------
>                 Key: YARN-6594
>                 URL: https://issues.apache.org/jira/browse/YARN-6594
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Konstantinos Karanasos
>            Assignee: Konstantinos Karanasos
>         Attachments: YARN-6594.001.patch
> This JIRA introduces a new SchedulingRequest object.
> It will be part of the {{AllocateRequest}} and will be used to define sizing 
> (e.g., number of allocations, size of allocations) and placement constraints 
> for allocations.
> Applications can use either this new object (when rich placement constraints 
> are required) or the existing {{ResourceRequest}} object.

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