[
https://issues.apache.org/jira/browse/PIG-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603859#action_12603859
]
Pi Song commented on PIG-158:
-----------------------------
I've mistaken aggregate as the same semantic as flat structure in my last post
:( . I admit your idea to overload Generate sounds better than mine. How about
this? We overload GENERATE by sticking List<AggregateFunc> with it. Does it
look alright? Then we still keep every nested plan with GENERATE and we do
aggregate(accumulate) only if we need to.
BTW, having accumulator explicitly is also a clean design. Don't know which one
is better.
> Rework logical plan
> -------------------
>
> Key: PIG-158
> URL: https://issues.apache.org/jira/browse/PIG-158
> Project: Pig
> Issue Type: Sub-task
> Components: impl
> Reporter: Alan Gates
> Assignee: Alan Gates
> Attachments: is_null.patch, logical_operators.patch,
> logical_operators_rev_1.patch, logical_operators_rev_2.patch,
> logical_operators_rev_3.patch, parser_changes.patch, parser_changes_v1.patch,
> parser_changes_v2.patch, parser_changes_v3.patch, parser_changes_v4.patch,
> ParserErrors.txt, udf_fix.patch, udf_funcSpec.patch, udf_return_type.patch,
> user_func_and_store.patch, visitorWalker.patch
>
>
> Rework the logical plan in line with
> http://wiki.apache.org/pig/PigExecutionModel
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
