[
https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013780#comment-13013780
]
Mridul Muralidharan commented on PIG-1881:
------------------------------------------
I have not looked at the patch in detail, but what I remember from work on ibis
was that :
a) Handling properties and property files was not clearly understood via the
api (probably 'cos I did not have access to the code).
b) Handling modules, etc was not properly handled.
c) Ditto for parameter substitutions, etc.
We ended up duplicating a lot of code from pig's Main just to get those working
because of the 'unconventional' way in which these are implemented currently.
> Need a special interface for Penny (Inspector Gadget)
> -----------------------------------------------------
>
> Key: PIG-1881
> URL: https://issues.apache.org/jira/browse/PIG-1881
> Project: Pig
> Issue Type: New Feature
> Components: impl
> Affects Versions: 0.9.0
> Reporter: Alan Gates
> Assignee: Laukik Chitnis
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: PIG-1881-4.patch, toolsserver.patch
>
>
> The proposed Penny tool needs access to Pig's new logical plan in order to
> inject code into the the dataflow. Once it has modified the plan it needs to
> then be able to hand back that modified plan and have Pig execute it.
> As we don't want to open this functionality up to general users, the proposal
> is to do this by subclasses PigServer with a new class that is marked as
> LimitedPrivate for Penny only. This class will provide calls to parse a Pig
> Latin script and return a logical plan, and one to take a logical plan and
> execute it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
