[
https://issues.apache.org/jira/browse/PIG-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551479#comment-14551479
]
Hitesh Shah commented on PIG-4429:
----------------------------------
To clarify, for inputs and outputs that are part of the tez-runtime-library, if
the convert-to-history-text flag is enabled, they will automatically setup the
history text as needed and eventually be pushed to ATS/timeline. This is not
done for any of the processors. The UI relies on the dag plan build phase to
setup the history text correctly so that it can eventually be published to ATS.
Tez makes no assumptions on the user payload ( for example it being serialized
config) and does not push this binary payload to ATS.
Didn't look at the patch in too much detail but if you are using the config
builders for the edges, explicitly setting up history text should not be
needed. However, for the pig processor, it would be useful to set it up with
the required useful config info.
> Add Pig alias information and Pig script to the DAG view in Tez UI
> ------------------------------------------------------------------
>
> Key: PIG-4429
> URL: https://issues.apache.org/jira/browse/PIG-4429
> Project: Pig
> Issue Type: Improvement
> Reporter: Rohini Palaniswamy
> Assignee: Daniel Dai
> Fix For: 0.15.0
>
> Attachments: PIG-4429-1.patch
>
>
> The DAG view displays vertex name, id, time duration, task and status
> information for each vertex. It would be good to add the pig alias and
> feature (join, group by, etc) information to a "Description" Field to give a
> clear idea of what that vertex is doing something similar to Lipstick. There
> was another suggestion to also have a "Code" section which can put part of
> the pig script relevant to that. Or the full pig script could be just set at
> the DAG level and users can go check on the alias with the pig script there.
> Most of the time, when multiple users are responsible for a pipeline it is
> easy to have the pig script also displayed instead of having to go to svn and
> git to find the script. Easy for pig team during investigation as well. Need
> to check on the memory constraints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
