[
https://issues.apache.org/jira/browse/TEZ-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993463#comment-13993463
]
Tsuyoshi OZAWA commented on TEZ-373:
------------------------------------
{quote}
Also, after that change I dont think TezUserPayload will not need to be a
Writable.
{quote}
I found one problem. Currently, we cannot remove Writable serde about user
payload from TezEntityDescriptor because there are no adapter methods between
DataInput for Writable and InputStream for Protobuf. Additionally, InputSpec,
OutputSpec, TaskSpec and GroupInputSpec) are using
TezEntityDescriptor#write(DataOutput)/readField(DataInput) methods. To solve
this problem, we should make the classes use serde with not via Writable but
via Protobuf objects. TEZ-305 is addresing the problem. Therefore, I updated a
patch with TezUserPayload which doesnt any changes in
{{TezEntityDescriptor#write()/readField()}} as a "temporal implementation" and
first step. Do you have better idea?
> Create UserPayload class
> ------------------------
>
> Key: TEZ-373
> URL: https://issues.apache.org/jira/browse/TEZ-373
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Tsuyoshi OZAWA
> Labels: newbie
> Attachments: TEZ-373.1.patch, TEZ-373.2.patch, TEZ-373.3.patch,
> TEZ-373.4.patch, TEZ-373.5.patch, TEZ-373.6.patch, TEZ-373.7.patch,
> TEZ-373.8.patch
>
>
> Currently Tez allows user payload to be passed as byte[]. Within Tez code is
> hard to understand where byte[] is userPayload and where is not user payload.
> If we create a TezUserPayload class that contains byte[] as a member then its
> much easier to search and identify in code.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
