[
https://issues.apache.org/jira/browse/TEZ-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999114#comment-13999114
]
Bikas Saha commented on TEZ-1119:
---------------------------------
I dont think we can have only 1 task do this since in the dynamic payload case,
each task can have a different payload. The task's IPOs could send a
size-delimited string to the AM and the AM could write it out using the
configured plugin after combining the strings from the IPOs. The string
combination should probably happen in the task itself after IPO.initialize() or
IPO.close(). If we do it on close then we may get the most accurate value since
the task may have received addition configuration events while running. In
general, we need to present all useful config information about the task ==
initial payload + addition configuration events.
> Support display of user payloads in Tez UI
> ------------------------------------------
>
> Key: TEZ-1119
> URL: https://issues.apache.org/jira/browse/TEZ-1119
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
>
> Applications like Pig rely heavily on configurations bundled in as part of
> the user payload for debugging. This requires each Input/Output/Processor's
> user payload to be converted into something that easily consumable by the UI
> layer to be displayed back to the user as meaningful data.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
