[
https://issues.apache.org/jira/browse/TEZ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180202#comment-14180202
]
Bikas Saha commented on TEZ-1666:
---------------------------------
[~hitesh][~sseth] From what I see, this can be simply fixed by documentation
since its just a question of what is the correct code to write. Changing a
Nullable return value to non-Nullable will not be possible later on and so I
was resisting changing the code.
However, if both of you feel that we should change this to be Nullable then
perhaps I am missing something. Please go ahead and make the change if you both
agree that its the right thing to do.
> 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)
