You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2015/05/20 00:32:02 UTC

[jira] [Commented] (PIG-4429) Add Pig alias information and Pig script to the DAG view in Tez UI

    [ https://issues.apache.org/jira/browse/PIG-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551370#comment-14551370 ] 

Rohini Palaniswamy commented on PIG-4429:
-----------------------------------------

Few comments:
    - Can you check with [~hitesh] if the conf in history text is still needed?  With conf being shown in Tez UI automatically for source/sinks now and dag/vertex (TEZ-986) in future that code is most likely not needed any more.
   - TezScriptState.get().getDAGScriptInfo(dag.getName()).getAliasLocation(tezOp) - In addition to the alias info can we append the getPigFeatures(tezOp) string to the description enclosed in braces. 

Can you attach a snapshot of how the vertex description shows in the DAG View UI if possible?

> 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)