[
https://issues.apache.org/jira/browse/TEZ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171761#comment-14171761
]
Siddharth Seth commented on TEZ-1666:
-------------------------------------
Ideally, UserPayload should be null - because that's what the user is not
specifying. If ProcessorDescriptor.setUserPayload were accepting a ByteBuffer
only, then it would be alright for UserPayload to be a valid object with a null
ByteBuffer payload.
> UserPayload should be null if the payload is not specified
> ----------------------------------------------------------
>
> Key: TEZ-1666
> URL: https://issues.apache.org/jira/browse/TEZ-1666
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Siddharth Seth
> Priority: Critical
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
