You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Alan Gates (JIRA)" <ji...@apache.org> on 2011/03/03 18:35:37 UTC
[jira] Created: (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
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
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
[jira] [Commented] (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Laukik Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012612#comment-13012612 ]
Laukik Chitnis commented on PIG-1881:
-------------------------------------
Yes, that is correct. None of the two methods change the state of the original DAG though, so I think it should be safe. Originally, it was using the clone() method in Graph, but since we were using an unconventional method for cloning, I opted for a new duplicate() method rather than overriding clone(). I assumed that the old methods were removed since they were no longer used, but I would like to know as well if there was some other reason.
> 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
[jira] [Commented] (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Xuefu Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013722#comment-13013722 ]
Xuefu Zhang commented on PIG-1881:
----------------------------------
I had a look at the patch. It appeared to me that there can be a simpler approach.
If the proper usage of ToolPigServer is as documented, I think we only need provide two APIs: one takes a query and returns a LogicalPlan instance, and another one takes a LogicalPlan instance and run it. Having said that, I don't think we need getPlans() method in ToolPigServer. Also, we wouldn't need cloning a logical plan in PigServer. And we need none of the methods that were reintroduced to PigServer.
Plus, I don't understand why we need PigPlans class. It doesn't seem to do anything or hide anything.
I think it's even better to use containment instead of inheritance. We can have a class which contains a PigServer instance, which only exposes the two API's mentioned above. This way, you can control what the user can perform on your class instance. Otherwise, who knows what's going to happen if I call ToolPigServer.registerNoRun(), and then ToolPigServer.registerQuery(), and then ToolPigServer.getPlan().
If it turns out user needs functionality of PigServer, they don't need to get it from ToolPigServer. He/she can just instantiate a PigServer instance. But for ToolPigServer, the only thing allowed should be just two above mentioned API.
With above discussion, in my opinion, there is no need for the cloning method. BTW, the original clone method had issue with line numbers.
> 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
[jira] [Updated] (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Laukik Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laukik Chitnis updated PIG-1881:
--------------------------------
Attachment: PIG-1881-4.patch
> 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
[jira] Commented: (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Ashutosh Chauhan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002405#comment-13002405 ]
Ashutosh Chauhan commented on PIG-1881:
---------------------------------------
I think instead of subclass approach, hook style interface might be better suited in this case. That way, user can register his hook (via config param) which Pig will dynamically instantiate and then invoke. This gets more power in hand of users as they are not limited by interface of PigServertools and also Pig needs to make no promises as hooks are owned by user and registered in runtime such that any modification in Pig's behavior is governed by their hook, not by Pig itself.
> 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: 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
[jira] Commented: (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Santhosh Srinivasan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002503#comment-13002503 ]
Santhosh Srinivasan commented on PIG-1881:
------------------------------------------
bq. 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.
Any specific reason for not opening this up? Just trying to understand why the Penny use case is special.
> 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: 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
[jira] [Commented] (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Mridul Muralidharan (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Laukik Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laukik Chitnis updated PIG-1881:
--------------------------------
Attachment: PIG-1881-4.patch
{noformat}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the total number of release audit warnings.
[exec]
{noformat}
> 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
[jira] [Commented] (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Alan Gates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012586#comment-13012586 ]
Alan Gates commented on PIG-1881:
---------------------------------
It looks like you brought back the PigServer.getCloneGraph and PigServer.Graph.duplicate methods after they were removed. Is that correct? I'm fine with that but I'd like to know who removed them and why to make sure we aren't breaking something.
Other than that question, patch looks good.
> 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
[jira] [Updated] (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Laukik Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laukik Chitnis updated PIG-1881:
--------------------------------
Attachment: (was: PIG-1881-4.patch)
> 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
[jira] Updated: (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Alan Gates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Gates updated PIG-1881:
----------------------------
Attachment: toolsserver.patch
This patch provides the requested interface. It has gone out of sync with trunk (it's about a month old now) and needs to be resynced.
> 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: 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
[jira] Commented: (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Alan Gates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004075#comment-13004075 ]
Alan Gates commented on PIG-1881:
---------------------------------
I don't want this to be a public interface at all, evolving or otherwise. That's why it's marked limited private. The reason for the one off interface is that this is a tool we think we should adopt and maintain.
> 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: 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
[jira] Commented: (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Alan Gates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003449#comment-13003449 ]
Alan Gates commented on PIG-1881:
---------------------------------
The reason for not opening this up is that it exposes the logical plan as an interface. That is not something we want to make any guarantees about from release to release. The same response applies to a hooks interface. The goal here is not to open up PigServer for users to extend. It is to make a one time extension necessary for a tool that will be maintained by the Pig team.
> 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: 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
[jira] [Resolved] (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Alan Gates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Gates resolved PIG-1881.
-----------------------------
Resolution: Fixed
Patch 4 checked in. Thank you Laukik.
> 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
[jira] Commented: (PIG-1881) Need a special interface for Penny
(Inspector Gadget)
Posted by "Santhosh Srinivasan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003547#comment-13003547 ]
Santhosh Srinivasan commented on PIG-1881:
------------------------------------------
The one time argument is a little bit difficult to understand. Can we instead open up the interface and mark it as evolving. It will help us lay the groundwork for allowing plug-in optimizers at different stages - logical, map-reduce, etc (assuming if we have such plans)
> 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: 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