hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-662) Enforce required parameters for all the protocols
Date Fri, 17 May 2013 06:31:19 GMT

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

Vinod Kumar Vavilapalli commented on YARN-662:

We can do it server side as well as on the client side, but clearly server-side is a must.
If isn't a big change, protocol by protocol, we should fix both the server side as well as
the client libraries. It'll be easier that way both for dev and review.

bq. Does this include making null checks etc on all incoming fields in the API handlers?
Yes, these would essentially be null checks.
> Enforce required parameters for all the protocols
> -------------------------------------------------
>                 Key: YARN-662
>                 URL: https://issues.apache.org/jira/browse/YARN-662
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Zhijie Shen
> All proto fields are marked as options. We need to mark some of them as requried, or
enforce these server side. Server side is likely better since that's more flexible (Example
deprecating a field type in favour of another - either of the two must be present)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message