[
https://issues.apache.org/jira/browse/PIG-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584795#comment-13584795
]
Prashant Kommireddi commented on PIG-3199:
------------------------------------------
Ok, I can understand the concerns and agree with you on not exposing LP.
What I stated earlier is exactly the info I need - using PigServer register
script/query and be able to determine the source/sinks. For eg, in the
following snippet I read a script "script.pig". I don't control the contents of
the script (written by other users) and as an admin would like to make sure I
can read the I/O paths being used here.
{code}
pigServer = new PigServer(ExecType.MAPREDUCE, conf);
InputStream in = fs.open("/foo/script.pig");
pigServer.registerScript(in);
{code}
script.pig
{code}
A = load '/apache/pig/*';
B = store A into '/google';
{code}
The idea with this patch was to be able to determine source (/apache/pig) and
sink (/google) and perform certain operations on it. Would be great if you
think it can be done in a way better than exposing any of LP/Operator.
> Expose LogicalPlan via PigServer API
> ------------------------------------
>
> Key: PIG-3199
> URL: https://issues.apache.org/jira/browse/PIG-3199
> Project: Pig
> Issue Type: Improvement
> Components: impl
> Affects Versions: 0.10.0
> Reporter: Prashant Kommireddi
> Assignee: Prashant Kommireddi
> Fix For: 0.12
>
> Attachments: PIG-3199.patch
>
>
> LogicalPlan could be exposed to user in order for one to make validations
> based on it. For eg, one could get Load/Store paths or other operators and be
> able to perform checks such as whether I/O paths are valid etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
