[YARN-662] [Umbrella] Enforce required parameters for all the protocols

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Zhijie Shen
• Reporter: Siddharth Seth
• Created: 09/May/13 21:38
• Updated: 08/Jan/15 02:34

Description

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)

Issue Links

• blocks: YARN-386 [Umbrella] YARN API Changes
• is blocked by: YARN-698 Review of Field Rules, Default Values and Sanity Check for ClientRMProtocol
• is blocked by: YARN-703 Review of Field Rules, Default Values and Sanity Check for RMAdminProtocol
• is blocked by: YARN-704 Review of Field Rules, Default Values and Sanity Check for AMRMProtocol
• is blocked by: YARN-705 Review of Field Rules, Default Values and Sanity Check for ContainerManager
• is related to: YARN-695 masterContainer and status are in ApplicationReportProto but not in ApplicationReport

Sub-Tasks

• Review of Field Rules, Default Values and Sanity Check for ContainerManager: Open
• Review of Field Rules, Default Values and Sanity Check for AMRMProtocol: Open
• Review of Field Rules, Default Values and Sanity Check for RMAdminProtocol: Open
• Review of Field Rules, Default Values and Sanity Check for ClientRMProtocol: Open