[
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
