[
https://issues.apache.org/jira/browse/PIG-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581915#action_12581915
]
Pi Song commented on PIG-154:
-----------------------------
Alan,
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?
Normal implementation:-
{noformat}
[Code] ==parser==> [AST] ==code_generator==> [Intermediate Instructions]
==native_code_generator==> [native_executable]
{noformat}
Pig implementation:-
{noformat}
Compile Time
[Code] ==parser==> [Intermediate Instructions(Logical Plan)]
==native_code_generator(Physical Plan Compiler)==> [native_executable]
{noformat}
> 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.
