[
https://issues.apache.org/jira/browse/PIG-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582012#action_12582012
]
Arun C Murthy commented on PIG-154:
-----------------------------------
bq. Sorry I don't quite understand what you tried to explain. Is having
LODefine in the logical plan due to the fact that we shortcut our processing
step?
Pi, Alan is referring to the fact that the newly introduced LODefine is
essentially a dummy LogicalOperator which is never used at all... it was
necessary since QueryParser.parse() currently returns a LogicalPlan (which
contains a LogicalOperator). Alan is pointing out that future work on the Pig
parsers should incorporate DEFINE like operators. Hope that helps ...
> Move DEFINE and STORE parsing into QueryParser from GruntParser
> ---------------------------------------------------------------
>
> Key: PIG-154
> URL: https://issues.apache.org/jira/browse/PIG-154
> Project: Pig
> Issue Type: Improvement
> Components: grunt
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Fix For: 0.1.0
>
> Attachments: PIG-154_0_20080319.patch, PIG-154_1_20080319.patch
>
>
> Currently GruntParser handles the parsing of DEFINE and STORE commands, it
> would be better to parse these in the main QueryParser since it has better
> infrastructure for expressions etc. which are really crucial for parsing UDFs
> etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
