You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Daniel Dai (JIRA)" <ji...@apache.org> on 2014/05/30 21:11:03 UTC
[jira] [Resolved] (PIG-3970) Merge Tez branch into trunk
[ https://issues.apache.org/jira/browse/PIG-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Dai resolved PIG-3970.
-----------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Patch committed to trunk. Thanks Cheolsoo, Rohini for review!
> Merge Tez branch into trunk
> ---------------------------
>
> Key: PIG-3970
> URL: https://issues.apache.org/jira/browse/PIG-3970
> Project: Pig
> Issue Type: New Feature
> Components: tez
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Fix For: 0.14.0
>
> Attachments: PIG-3970-1.no_space_change.patch, PIG-3970-1.patch, PIG-3970-final.patch
>
>
> After months of development, I feel tez branch reaches to a point we can merge back into trunk. The merge will not introduce any known regression, that is:
> 1. All existing unit tests pass in mr mode
> 2. All existing e2e tests pass in mr mode
> 3. No backward-incompitable changes
> The tez branch is stable enough, that is:
> 1. All migrated unit tests pass in tez mode
> 2. Vast majority of e2e tests pass in tez mode, minor number of failures are properly investigated
> Ongoing tez work can continue after the merge. It is unlikely major changes to other part of Pig code will be involved going forward.
> Known limitations for Pig on tez at this moment:
> 1. Some unit tests are not ported (PIG-3840)
> 2. Several operators are missing: native, merge-sparse join, collected cogroup
> 3. auto-parallelism is not in (PIG-3846)
--
This message was sent by Atlassian JIRA
(v6.2#6252)