hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunther Hagleitner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-726) Stop printing scope as part of Operator.toString()
Date Wed, 25 Mar 2009 23:10:52 GMT

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

Gunther Hagleitner 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 (the scope is not really used right now as I understand it. It's
a leftover from times when pig was designed as a standalone server). That way each operator
will say: ForEach 1-4 (or 2-4 depending on how many instances of the pig server you have in
your jvm.)

The alternative is to change all the logical operators name() function. They look something
like: return <some info> + mKey.scope + "-" + mKey.id; For physical operators we could
get away with the proposed change to key.toString() function.

That seems more painful.

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

View raw message