pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olga Natkovich (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-21) Show more details about the current execution context
Date Mon, 05 Nov 2007 20:47:50 GMT

    [ https://issues.apache.org/jira/browse/PIG-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540269

Olga Natkovich commented on PIG-21:

Hi Andrzej,

Thanks for contributing! This set of commands is very useful and in fact we had users asking
for some of them.

I applied your patch and played a little bit with the commands and they work well and the
code looks good. I found a couple of things that don't seem quite right:

(1) show env does not seem to show the URL for the job tracker which is my understanding of
what you were trying to do. Instead it shows name of the class.
(2) It would be nice if show aliases showed them in the order of definition or dependency
(3) In show aliases, if you redefine the alias, it shows twice and it is hard to tell which
one is the latest one.

Points (2) and (3) can be demonstrated with the following pig script:

A = load 'myfile' using PigStorage();
A = load 'myfile' using PigStorage() as (a,b,c);
B = filter A by b > '25';
C = group B by a;
D = for each C generate flatten(group), B;

show aliases;

> Show more details about the current execution context
> -----------------------------------------------------
>                 Key: PIG-21
>                 URL: https://issues.apache.org/jira/browse/PIG-21
>             Project: Pig
>          Issue Type: Improvement
>          Components: grunt
>    Affects Versions: 0.1.0
>            Reporter: Andrzej Bialecki 
>            Priority: Minor
>             Fix For: 0.1.0
>         Attachments: context.patch
> After a long interactive session with grunt I lost track of what kind of queries I defined,
and then re-defined. It would be nice to have the ability to show all defined aliases, and
other context variables, such as the filesystem, jobTracker, user jars and Configuration.

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

View raw message