[
https://issues.apache.org/jira/browse/TEZ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172826#comment-14172826
]
Bikas Saha commented on TEZ-1666:
---------------------------------
The disadvantage is that if there is any additional data that can be passed via
the UserPayload object. E.g. all the user overriden client side confs etc. then
we would not be able to do so because we would have been passing null to the
user and changing that back to be non-null would be a regression. If this can
be fixed/clarified using javadoc and then that would be preferable. Changing
something from null to non-null can be disruptive later on and I am not
confident our user payload story is done for now.
> 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)
