[
https://issues.apache.org/jira/browse/PIG-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966262#action_12966262
]
Richard Ding commented on PIG-1479:
-----------------------------------
Thanks Julien.
As for the second comment, there is a third option, namely separating frontend
(control flow code) from backend (scripting UDFs) by putting them in different
files, and requires control flow writer to explicitly register UDFs in his/her
script. For example, in control flow file script.py:
{code}
pig.registerUDF("myudfs.py", "mynamespace")
# control flow and PIG pipelines that use UDFs defined in myudfs.py
{code}
The advantage of this is that only UDF files are shipped to the backend while
control flow file (and its dependencies) remains in front end. Obviously, the
disadvantage is that you can't put everything in one file.
> 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-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.
