GitHub user gatorsmile opened a pull request:

    https://github.com/apache/spark/pull/10398

    [SPARK-12287] [SQL] Support Unsafe Row in MapPartitions/MapGroups/CoGroup

    Support Unsafe Row in MapPartitions/MapGroups/CoGroup. 
    
    Added a test case for MapPartitions. Since MapGroups and CoGroup are built 
on AppendColumns, all the related dataset test cases already can verify the 
correctness when MapGroups and CoGroup processing unsafe rows. 
    
    @davies @cloud-fan Not sure if my understanding is right, please correct 
me. Thank you!

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gatorsmile/spark unsafeRowMapGroup

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/10398.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #10398
    
----
commit 4475706874082d19fcc7acb687689fa8d353a8aa
Author: gatorsmile <[email protected]>
Date:   2015-12-20T00:41:37Z

    comment it out.

commit 969f6640f6c5636cd32600d1bfd290bf73a386ea
Author: gatorsmile <[email protected]>
Date:   2015-12-20T04:44:26Z

    Support UnsafeRow in MapPartitions/MapGroups/CoGroup.

commit 6d0c8f50241fc2cdbd110e77c90733f4595320ef
Author: gatorsmile <[email protected]>
Date:   2015-12-20T04:47:40Z

    Merge remote-tracking branch 'upstream/master' into unsafeRowMapGroup

commit a70e95c9109a753dd2528c5544ddd9ff86722397
Author: gatorsmile <[email protected]>
Date:   2015-12-20T04:49:55Z

    converge.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to