[
https://issues.apache.org/jira/browse/PIG-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969571#action_12969571
]
Richard Ding commented on PIG-1479:
-----------------------------------
Thanks Alan,
bq. This patch makes changes to the public interface
PigProgressNotificationListener. It's ok, since it's marked evolving. Do we
know how many people are using this and what we'll need to do to mitigate the
changes for them?
This interface is available only in Pig 0.8 which is just ready to release. So
not many people are using it. On the other hand it's too late to get into 0.8.
The reason for the change is that the embedded script could contain multiple
Pig scripts and Pig runtime needs to tell users from which script they get the
notification.
bq. PigPipeline needs better javadoc comments at the class level. The current
javadocs confuse it with the defined Pig class.
Will do.
bq. Rather than the Pig class detailed in the design doc this patch has
ScriptPigServer, which has a slightly different interface. Does this represent
a change to the design or is there a yet to be built Pig class?
The patch breaks the Pig class interface into several class: ScriptPigServer to
register or define in global scope, to compile a Pig Latin script into a
PigPipeline object. PigPipeline binds a set of variables and generates a
BoundPigline object which then runs the bound pipeline. Embedded script writers
will have access to a ScriptPigServer object called "pig" in the script.
bq. Do we need two classes BoundPipeline and MultiBoundPipeline? Could we
instead have just BoundPipeline, and then for each run method there would be:
...
I went back and forth between these two approaches. I'm fine with a single
BoundPipeline class with two different run/runSingle method.
bq. We need to mark the availability and stability of the ScriptEngine
interface. I suspect it is Public Evolving.
Will do.
> Embed Pig in scripting languages
> --------------------------------
>
> Key: PIG-1479
> URL: https://issues.apache.org/jira/browse/PIG-1479
> Project: Pig
> Issue Type: New Feature
> Reporter: Julien Le Dem
> Assignee: Richard Ding
> Fix For: 0.9.0
>
> Attachments: PIG-1479.patch, PIG-1479_2.patch, PIG-1479_3.patch,
> PIG-1479_4.patch, pig-greek-test.tar, pig-greek-test.tar, pig-greek.tgz
>
>
> It should be possible to embed Pig calls in a scripting language and let
> functions defined in the same script available as UDFs.
> This is a spin off of https://issues.apache.org/jira/browse/PIG-928 which
> lets users define UDFs in scripting languages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.