[TEZ-1666] UserPayload should be null if the payload is not specified

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.5.2
• Target Version/s: 0.5.2
• Hadoop Flags: Incompatible change
• Assignee: Siddharth Seth
• Reporter: Siddharth Seth
• Created: 14/Oct/14 23:53
• Updated: 08/Nov/14 20:25
• Resolved: 29/Oct/14 21:23

Description

As an example in the ProcessorDescriptor - if no payload is specified, context.getUserPayload should return null.

SleepProcessor has an explicit check for a null payload, to enable default sleep value - which fails.

Marking as critical since this is an API behaviour inconsistency.