[
https://issues.apache.org/jira/browse/TEZ-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033449#comment-14033449
]
Siddharth Seth commented on TEZ-1119:
-------------------------------------
bq. I was thinking of providing hooks via the Context objects exposed to
various runtime components for sending data to history.
That works as well. I guess what needs to be considered is whether something
like a VertexManagerPlugin should be allowed to publish data for a different
entity (Vertex or DAG vs VertexManager only).
bq. A similar API could be exposed from the DAGClient too ( but not from
TezClient ). For a client to be able publish data before the DAG runs, it could
do its own thing and then allow Tez to reference the app specific timeline
entities.
>From an offline discussion, this will likely end up going via non mandatory
>APIs on the DAG itself - to allow Tez to take care of linking and publishing
>in the correct context.
> 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
> Attachments: TEZ-1119.wip.patch
>
>
> 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)
