You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2016/04/06 20:01:25 UTC

[jira] [Commented] (PIG-4854) Merge spark branch to trunk

    [ https://issues.apache.org/jira/browse/PIG-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228763#comment-15228763 ] 

Rohini Palaniswamy commented on PIG-4854:
-----------------------------------------

Will do 50% of it this weekend and rest next week. Going to take at least two weeks as me and Daniel are not very familiar with Spark and the patch is really huge. We will try to speed it up by focusing first on the core changes and then Spark changes.  

 [~dvryaboy] and [~julienledem],
    If you folks get time, please do a very high level review to see how the design has come out. Though it started with spork code base developed by you folks, it has undergone a lot of change.

> Merge spark branch to trunk
> ---------------------------
>
>                 Key: PIG-4854
>                 URL: https://issues.apache.org/jira/browse/PIG-4854
>             Project: Pig
>          Issue Type: Task
>            Reporter: Pallavi Rao
>         Attachments: PIG-On-Spark.patch
>
>
> Believe the spark branch will be shortly ready to be merged with the main branch (couple of minor patches pending commit), given that we have addressed most functionality gaps and have ensured the UTs are clean. There are a few optimizations which we will take up once the branch is merged to trunk.
> [~xuefuz], [~rohini], [~daijy],
> Hopefully, you agree that the spark branch is ready for merge. If yes, how would like us to go about it? Do you want me to upload a huge patch that will be merged like any other patch or do you prefer a branch merge?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)