[
https://issues.apache.org/jira/browse/PIG-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881772#action_12881772
]
Richard Ding commented on PIG-1333:
-----------------------------------
The unit test failures are not related to the patch (l run core tests locally
and it's successful). Release audit warnings are all html related, and
additional javac warnings are due to using a couple of deprecated Hadoop
classes.
I'm going to commit the patch shortly.
> API interface to Pig
> --------------------
>
> Key: PIG-1333
> URL: https://issues.apache.org/jira/browse/PIG-1333
> Project: Pig
> Issue Type: Improvement
> Reporter: Olga Natkovich
> Assignee: Richard Ding
> Fix For: 0.8.0
>
> Attachments: PIG-1333.patch, PIG-1333_1.patch, PIG-1333_2.patch,
> PIG-1333_3.patch
>
>
> It would be nice to make Pig more friendly for applications like workflow
> that would be executing pig scripts on user behalf.
> Currently, they would have to use pig command line to execute the code;
> however, this has limitation on the kind of output that would be delivered.
> For instance, it is hard to produce error information that is easy to use
> programatically or collect statistics.
> The proposal is to create a class that mimics the behavior of the Main but
> gives users a status object back. The the main code of pig would look
> somethig like:
> public static void main(String args[])
> {
> PigStatus ps = PigMain.exec(args);
> exit (PigStatus.rc);
> }
> We need to define the following:
> - Content of PigStatus. It should at least include
> * return code
> * error string
> * exception
> * statistics
> - A way to propagate the status class through pig code
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
