hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-21) Show more details about the current execution context
Date Thu, 15 Nov 2007 21:15:43 GMT

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

Andrzej Bialecki  commented on PIG-21:

The problem with JobTracker URL can be solved by the following snippet:

			if (ctx.getExecType() == ExecType.MAPREDUCE)
				System.out.println("Job tracker: " + JobTracker.getAddress(ctx.getConf()));

However, I'm not sure how to solve the other issues that you pointed out, I still know too
little about Pig internals ... There are no obvious places in PigServer or PigContext that
could provide this information - in case of (2) my understanding is that the dependency order
is determined just prior to store(), using IntermedResult.compile(), so I don't think it's
possible to show this dependency order without specifying which alias we want to store.

In case of (3), I think this is a problem with IntermedResult.lp.getSchema(), which retains
the original alias that it was assigned to (or maybe I'm totally confused ...).

So, for now I'm not able to fix these issues.

> 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