[
https://issues.apache.org/jira/browse/PIG-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193321#comment-13193321
]
Jie Li commented on PIG-2423:
-----------------------------
Oh I didn't notice that and sure we need to mention that.
Just curious if it's possible to enable the combiner for the co-group? I
believe it's worthy to make such effort to fully take the advantage of co-group
against the join in certain cases.
Another more general approach might be enriching the multi-query optimization
such that the common partitioning between two jobs is recognized.
Shall we open new tickets to discuss them?
> document use case where co-group is better choice than join
> ------------------------------------------------------------
>
> Key: PIG-2423
> URL: https://issues.apache.org/jira/browse/PIG-2423
> Project: Pig
> Issue Type: Improvement
> Components: documentation
> Reporter: Thejas M Nair
> Fix For: 0.10
>
>
> Optimization rules 2 and 3 suggested in
> https://issues.apache.org/jira/secure/attachment/12506841/pig_tpch.ppt
> (PIG-2397) recommend the use of co-group instead of join in certain cases.
> These should be documented in pig performance page.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
