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/08/04 20:42:16 UTC

[jira] [Commented] (TEZ-1194) Make TezUserPayload user facing for payload specification and change to ByteBuffer

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

Bikas Saha commented on TEZ-1194:
---------------------------------

[~ozawa] This is a blocker for 0.5. So it would great if it can be done by this week. If you are busy then can someone else take this over?

> Make TezUserPayload user facing for payload specification and change to ByteBuffer
> ----------------------------------------------------------------------------------
>
>                 Key: TEZ-1194
>                 URL: https://issues.apache.org/jira/browse/TEZ-1194
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>            Assignee: Tsuyoshi OZAWA
>            Priority: Blocker
>         Attachments: TEZ-1194.1.patch, TEZ-1194.2.patch
>
>
> Now that we have TezUserPayload being used internally to represent user payload it may be useful to make it user facing on the API for specifying payloads. Advantages
> 1) Clear code for the user instead of having untyped byte[] everywhere
> 2) Lets us internally evolve the representation of user payload and make it more efficient without having to break APIs. We can start with TezUserPayload(byte[]) and then move on to TezUserPayload(ByteBuffer) and so on while maintaining backwards compatibility without needing to add new methods. Old code can be translated within TezUserPayload while user migrates the code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)