[
https://issues.apache.org/jira/browse/TEZ-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032893#comment-14032893
]
Hitesh Shah commented on TEZ-1119:
----------------------------------
[~sseth] I was thinking of providing hooks via the Context objects exposed to
various runtime components for sending data to history. The context objects
would augment the history data with additional source information and direct it
to the appropriate history impl ( i.e. one of direct to ATS, to AM for central
history logging or redirect to AM which in turn could send it to ATS ).
Given that most of the timeline data is referenced via the dag/vertex/task ids,
the above seemed to make more sense. 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.
> 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)
