[
https://issues.apache.org/jira/browse/PIG-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584776#comment-13584776
]
Prashant Kommireddi commented on PIG-3199:
------------------------------------------
It's not exposed at the moment but a part of this patch. I was not aware of
plans to make changes to LogicalPlan at the interface level. Just noticed this
for OperatorPlan and it makes sense.
{code}
@InterfaceAudience.Private
@InterfaceStability.Unstable
{code}
If that's the case, can we expose only a couple methods to get a handle on
source/sinks?
{code}
public List<Operator> getSources();
public List<Operator> getSinks();
{code}
> 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
