Github user ueshin closed the pull request at:
https://github.com/apache/spark/pull/790
---
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 enabl
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/790#issuecomment-43279550
@ueshin not sure how come github didn't close this pull request. Do you
mind closing it? The change has been merged.
---
If your project is set up for it, you can reply to t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/790#issuecomment-43204087
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15024/
---
If your project
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/790#issuecomment-43282262
Thanks! I'll close it.
---
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/790#issuecomment-43204085
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/790#issuecomment-43245088
Nice. We stopped using this before because it was breaking serialization
of Rows (since they are also Seqs). I guess as long as we run it after
registering Rows specifi
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/790#issuecomment-43246060
Thanks. Merged into master & branch-1.0.
---
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
