Jason Lowe commented on YARN-4225:

Yes, I was thinking the client would refrain from reporting on a field it knew 
wasn't provided.  However I think having a getPreemptionDisabled and 
hasPreemptionDisabled methods exposed outside the protobuf is very confusing -- 
someone might call has when they should be calling get.  Maybe a name like 
"isPreemptionDisabledValid" or something would be more clear.

> Add preemption status to yarn queue -status for capacity scheduler
> ------------------------------------------------------------------
>                 Key: YARN-4225
>                 URL: https://issues.apache.org/jira/browse/YARN-4225
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler, yarn
>    Affects Versions: 2.7.1
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>            Priority: Minor
>         Attachments: YARN-4225.001.patch, YARN-4225.002.patch

This message was sent by Atlassian JIRA

Reply via email to