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 2008/12/31 22:05:44 UTC
[jira] Commented: (PIG-572) A PigServer.registerScript() method,
which lets a client programmatically register a Pig Script.
[ https://issues.apache.org/jira/browse/PIG-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660148#action_12660148 ]
Alan Gates commented on PIG-572:
--------------------------------
The code in the patch looks fine. I have a couple of questions:
# What's the use case driving this? If a user has their pig script in a file why do we expect them to be using PigServer directly instead of grunt?
# Why does the logical plan need to be serializable?
> A PigServer.registerScript() method, which lets a client programmatically register a Pig Script.
> ------------------------------------------------------------------------------------------------
>
> Key: PIG-572
> URL: https://issues.apache.org/jira/browse/PIG-572
> Project: Pig
> Issue Type: New Feature
> Affects Versions: types_branch
> Reporter: Shubham Chopra
> Priority: Minor
> Fix For: types_branch
>
> Attachments: registerScript.patch
>
>
> A PigServer.registerScript() method, which lets a client programmatically register a Pig Script.
> For example, say theres a script my_script.pig with the following content:
> a = load '/data/my_data.txt';
> b = filter a by $0 > '0';
> The function lets you use something like the following:
> pigServer.registerScript("my_script.pig");
> pigServer.registerQuery("c = foreach b generate $2, $3;");
> pigServer.store("c");
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.