Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100787889
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/5830#issuecomment-100787907
Merged build started.
---
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/6050#issuecomment-100798432
Merged build started.
---
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 jerryshao opened a pull request:
https://github.com/apache/spark/pull/6050
[Streaming][minor] Close files correctly when iterator is finished in
streaming WAL recovery
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6049#issuecomment-100788564
Can one of the admins verify this patch?
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6050#issuecomment-100798511
[Test build #32378 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32378/consoleFull)
for PR 6050 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6050#issuecomment-100798418
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/5996#issuecomment-100783418
Jenkins, retest this please.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5886#issuecomment-100784958
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/5886#issuecomment-100785040
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5996#issuecomment-100785267
[Test build #32375 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32375/consoleFull)
for PR 5996 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100781403
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100781380
[Test build #32368 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32368/consoleFull)
for PR 6048 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100781399
Merged build finished. Test 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 your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5996#issuecomment-100784939
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/5996#issuecomment-100785039
Merged build started.
---
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/5868#issuecomment-100792625
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5868#issuecomment-100792595
[Test build #32373 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32373/consoleFull)
for PR 5868 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5868#issuecomment-100792627
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5798#issuecomment-100792898
Merged build finished. Test 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 your
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100792972
It looks like py4j can not recognize [T: ClassTag] for RankingMetrics.
If I removed [T: ClassTag] and specify the type (for example: Int) of
RankingMetrics, py4j
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5798#issuecomment-100792901
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5798#issuecomment-100792883
[Test build #32374 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32374/consoleFull)
for PR 5798 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6048#issuecomment-100782145
Merging to master and branch-1.4. Thanks for fixing this!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6048
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100788024
[Test build #32377 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32377/consoleFull)
for PR 5830 at commit
GitHub user BryanCutler opened a pull request:
https://github.com/apache/spark/pull/6049
[SPARK-7522] [EXAMPLES] Removed angle brackets from dataFormat option
As is, to specify this option on command line, you have to escape the angle
brackets.
You can merge this pull request into
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5886#issuecomment-100785402
[Test build #32376 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32376/consoleFull)
for PR 5886 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5886#issuecomment-100806266
Merged build finished. Test 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 your
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6049#issuecomment-100823171
Ah, so you literally have to write `--\dataFormat\`? definitely an
oversight then. LGTM
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6049#issuecomment-100823194
ok to test
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6049#issuecomment-100823359
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100861825
[Test build #32379 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32379/consoleFull)
for PR 5526 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100861852
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6049#issuecomment-100866965
[Test build #32380 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32380/consoleFull)
for PR 6049 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6049#issuecomment-100866991
Merged build finished. Test 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 your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6049#issuecomment-100866992
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100869450
[Test build #32381 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32381/consoleFull)
for PR 6003 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5996#issuecomment-100817659
Merged build finished. Test 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 your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5996#issuecomment-100817660
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100814789
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6049#issuecomment-100823625
[Test build #32380 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32380/consoleFull)
for PR 6049 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5835#issuecomment-100841145
@preeze are you able to rebase and undo the `!isInInterpreter` change? And
perhaps open a second JIRA for the logic error? this one PR can cover them
both. This would be
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100861854
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100869221
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/6003#issuecomment-100869237
Merged build started.
---
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 WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/6051
[SPARK-7524][YARN]add configs for keytab and principal, move originals to
internal
https://issues.apache.org/jira/browse/SPARK-7524
You can merge this pull request into a Git repository by
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100814786
Merged build finished. Test 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 your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6050#issuecomment-100831384
Merged build finished. Test 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 your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6050#issuecomment-100831387
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6050#issuecomment-100831372
[Test build #32378 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32378/consoleFull)
for PR 6050 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/6050#issuecomment-100872106
Thank for your review @srowen , both way are OK.
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100807482
retest this please
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6049#issuecomment-100823382
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5886#issuecomment-100806231
[Test build #32376 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32376/consoleFull)
for PR 5886 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5886#issuecomment-100806269
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100808506
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/5526#issuecomment-100808583
Merged build started.
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/4622#discussion_r30020688
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/AffinityPropagation.scala
---
@@ -0,0 +1,497 @@
+/*
+ * Licensed to the Apache
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5996#issuecomment-100817644
[Test build #32375 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32375/consoleFull)
for PR 5996 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/4467#discussion_r30020503
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -81,12 +112,14 @@ class ReceiverTracker(ssc:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100814774
[Test build #32377 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32377/consoleFull)
for PR 5830 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6051#issuecomment-100871171
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/6051#issuecomment-100871212
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100809961
[Test build #32379 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32379/consoleFull)
for PR 5526 at commit
Github user DoingDone9 commented on the pull request:
https://github.com/apache/spark/pull/5972#issuecomment-100823894
@marmbrus @yhuai @scwf
---
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 steveloughran commented on the pull request:
https://github.com/apache/spark/pull/6033#issuecomment-100831678
Jetty would catch them and generate a 500 response with no body, and not
log it *as far as I could find*.
This patch catches and logs via the spark-log4j
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6050#issuecomment-100839599
Seems reasonable to me. Is the `reader.close _` syntax needed or is just
`reader.close` sufficient? Just curious mostly.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6051#issuecomment-100871806
[Test build #32382 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32382/consoleFull)
for PR 6051 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6051#issuecomment-100872558
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/6052#issuecomment-100880945
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/6044#issuecomment-100881048
Merged build started.
---
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/6052#issuecomment-100881049
Merged build started.
---
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 adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/6027#issuecomment-100886341
For the idea of `getDate` and `setDate` interface I think it is already
rejected in #2284 . And I'm working on partitioning column already...
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6053#issuecomment-100899453
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/5707#issuecomment-100893892
Merged build started.
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5908#discussion_r30031423
--- Diff:
core/src/main/scala/org/apache/spark/storage/ExternalBlockStore.scala ---
@@ -113,7 +143,13 @@ private[spark] class ExternalBlockStore(blockManager:
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5908#discussion_r30031387
--- Diff:
core/src/main/scala/org/apache/spark/storage/TachyonBlockManager.scala ---
@@ -120,6 +134,16 @@ private[spark] class TachyonBlockManager() extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6052#issuecomment-100881304
[Test build #32384 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32384/consoleFull)
for PR 6052 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100891802
[Test build #32386 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32386/consoleFull)
for PR 5526 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6053#issuecomment-100899501
Merged build started.
---
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/5707#issuecomment-100893862
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/5526#issuecomment-100893869
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/6051#issuecomment-100872578
Merged build started.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/5871
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5933#discussion_r30031656
--- Diff: docs/sql-programming-guide.md ---
@@ -1253,7 +1253,12 @@ This command builds a new assembly jar that includes
Hive. Note that this Hive a
on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6051#issuecomment-100891472
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6051#issuecomment-100891474
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100891571
Merged build started.
---
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/5526#issuecomment-100891553
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100894151
[Test build #32381 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32381/consoleFull)
for PR 6003 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100896231
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100896236
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5526#issuecomment-100893916
Merged build started.
---
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/6051#issuecomment-100896956
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6051#issuecomment-100896917
[Test build #32382 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32382/consoleFull)
for PR 6051 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6044#issuecomment-100896192
[Test build #32385 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32385/consoleFull)
for PR 6044 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6051#issuecomment-100896951
Merged build finished. Test 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 your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100894167
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100894165
Merged build finished. Test 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 your
1 - 100 of 896 matches
Mail list logo
