You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2014/10/15 02:03:17 UTC

[jira] [Commented] (TEZ-1666) UserPayload should be null if the payload is not specified

    [ https://issues.apache.org/jira/browse/TEZ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171736#comment-14171736 ] 

Bikas Saha commented on TEZ-1666:
---------------------------------

Not sure what is expected to be null. TezUserPayload object is expected to be not null. TezUserPayload.getPayload() is expected to be null. This enables us to add some functionality to TezUserPayload itself in addition to the user ByteBuffer.

> 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)