Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/717#discussion_r12564572
--- Diff: core/src/main/scala/org/apache/spark/util/ClosureCleaner.scala ---
@@ -181,6 +184,26 @@ private[spark] object ClosureCleaner extends Logging {
}
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/729#issuecomment-42913020
Seems we are adding more `Project`s (for example, `Project
[i_brand_id#224:0,i_item_sk#217:1,i_brand#225:2]` after `Filter
(i_manufact_id#70:13 = 436)`). Do we need those
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/739#issuecomment-42913115
Merged build finished.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/339#issuecomment-42914064
Merged build finished.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/339#issuecomment-42914065
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14933/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/339#issuecomment-42909668
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/736#issuecomment-42913289
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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/746#issuecomment-42902460
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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/746#issuecomment-42902462
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14911/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/717#issuecomment-42913622
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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/731#issuecomment-42914808
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.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/702
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/746#issuecomment-42907887
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14918/
---
If your project
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/749
SPARK-1623: Use File objects instead of string's in HTTPBroadcast
This seems strictly better, and I think it's justified only the grounds of
clean-up. It might also fix issues with path
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/670#issuecomment-42919230
@mengxr should this go into 1.0? CCing @pwendell, it can be in the next RC.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
301 - 315 of 315 matches
Mail list logo
