[
https://issues.apache.org/jira/browse/OOZIE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101915#comment-13101915
]
Hadoop QA commented on OOZIE-308:
---------------------------------
mislam77 remarked:
The proposal is to modify the current PigMain to accommodate PigRunner and old
Main.amin() at the same time.
However, we want to keep the old pig main temporarily in different name. The
reason is operational.
Pig is used extensively in the production. PigRunner is not used by anybody
yet. Oozie will be the first user. That's why, we are expecting some issues
that might slip our Oozie QE too.
The plan is: if that happens for any use case, we could ask that user to use
the old main by adding a new configuration in workflow.xml. That way, the user
will be unblocked for the time being. At the same time, we would work with pig
team to resolve the root cause of using PigRunner.
This is just for sometime until we fell comfortable with the new API. After
that we will throw away that undocumented code.
> GH-480: Support new Pig API to submit pig job
> ---------------------------------------------
>
> Key: OOZIE-308
> URL: https://issues.apache.org/jira/browse/OOZIE-308
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> In addition of supporting old pig release, oozie needs to support PigRunner
> API for pig 0.8+.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
