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

Thejas M Nair commented on PIG-726:
-----------------------------------

> I've made a simpler change that had similar effects in the multiquery branch. 
> I basically set the scope to an integer 
That will certainly help, I think we can use this fix. Or we can change the 
scope part to an empty string.
You are right that changing OperatorKey.toString() will not help in case of 
explain of Logical Plan, name() functions would have had to change.


> Stop printing scope as part of Operator.toString()
> --------------------------------------------------
>
>                 Key: PIG-726
>                 URL: https://issues.apache.org/jira/browse/PIG-726
>             Project: Pig
>          Issue Type: Improvement
>            Reporter: Thejas M Nair
>
> When an operator is printed in pig, it prints a string with the user name and 
> date at which the grunt shell was started. This information is not useful and 
> makes the output very verbose.
> For example, a line in explain is like -
> ForEach tejas-Thu Mar 19 11:25:23 PDT 2009-4 Schema: {themap: map[ ]} Type: 
> bag
> I am proposing that it should change to -
> ForEach (id:4) Schema: {themap: map[ ]} Type: bag
> That string comes from scope in OperatorKey class. We don't use make use of 
> it anywhere, so we should stop printing it. The change is only in 
> OperatorKey.toString();

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to