GitHub user jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/10636
[MINOR] Fix for BUILD FAILURE for Scala 2.11
It was introduced in 917d3fc069fb9ea1c1487119c9c12b373f4f9b77
/cc @cloud-fan @rxin
You can merge this pull request into a Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10636#issuecomment-169587113
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10424#issuecomment-166469356
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/10424#issuecomment-166468677
Test FAILed.
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/10424#issuecomment-166468643
**[Test build #48138 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48138/consoleFull)**
for PR 10424 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10424#issuecomment-166471189
**[Test build #48143 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48143/consoleFull)**
for PR 10424 at commit
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/10424
[Minor]Fix typos in JavaStreamingContext
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zsxwing/spark typo
Alternatively you can review and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10424#issuecomment-166461313
**[Test build #48138 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48138/consoleFull)**
for PR 10424 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10424#issuecomment-166468676
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/10424#issuecomment-166529126
I've merged this in master & branch-1.6.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10424#issuecomment-166508984
**[Test build #48143 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48143/consoleFull)**
for PR 10424 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10424#issuecomment-166509027
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/10424#issuecomment-166509026
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10424
---
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/10424#issuecomment-166511323
LGTM
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-132141189
The test failures must be spurious. The fix must be correct since there is
no method called `getBlockLocation` anywhere now. Merging ...
---
If your project is set up
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-132167352
thanks
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8238
---
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/8238#issuecomment-132047727
[Test build #41090 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41090/consoleFull)
for PR 8238 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-132044748
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/8238#issuecomment-132045995
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/8238#issuecomment-132045934
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-131819722
LGTM
---
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
GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/8238
[MINOR] fix the comments in IndexShuffleBlockResolver
it might be a typo introduced at some moment or some left over after some
renaming..
the name of the method accessing the index
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-131844799
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/8238#issuecomment-131846283
[Test build #41021 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41021/consoleFull)
for PR 8238 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-131820013
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/8238#issuecomment-132074290
[Test build #41090 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41090/console)
for PR 8238 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-132074474
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/8238#issuecomment-132074479
Test FAILed.
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/8238#issuecomment-131901952
**[Test build #41021 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41021/console)**
for PR 8238 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-131902613
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/8238#issuecomment-131902607
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/8238#issuecomment-131914736
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/8238#issuecomment-131917063
[Test build #41040 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41040/consoleFull)
for PR 8238 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-131914678
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/8238#issuecomment-131963263
Test FAILed.
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/8238#issuecomment-131963194
[Test build #41040 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41040/console)
for PR 8238 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8238#issuecomment-131963260
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/6469#issuecomment-106589930
[Test build #33677 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33677/consoleFull)
for PR 6469 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6469#issuecomment-106589799
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/6469#issuecomment-106589829
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 mengxr opened a pull request:
https://github.com/apache/spark/pull/6469
[MINOR] fix RegressionEvaluator doc
`make clean html` under `python/doc` returns
~~~
/Users/meng/src/spark/python/pyspark/ml/evaluation.py:docstring of
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6455#issuecomment-106582501
[Test build #33669 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33669/consoleFull)
for PR 6455 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6455#issuecomment-106582510
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6469#issuecomment-106618921
[Test build #33677 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33677/consoleFull)
for PR 6469 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6469#issuecomment-106618928
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6455#issuecomment-106589251
lgtm master 1.4 thanks.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/6455
---
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 the pull request:
https://github.com/apache/spark/pull/6455#issuecomment-106544048
Jenkins, test 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6455#issuecomment-106547577
[Test build #33669 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33669/consoleFull)
for PR 6455 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6455#issuecomment-106545747
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/6455#issuecomment-106545829
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/6469#issuecomment-106681467
Merged into master and branch-1.4.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6469
---
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 the pull request:
https://github.com/apache/spark/pull/6455#issuecomment-106441973
LGTM
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6455#issuecomment-106442026
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 andrewor14 opened a pull request:
https://github.com/apache/spark/pull/5883
[Minor] Fix python test typo?
I suspect haven't been using anaconda in tests in a while. I wonder if this
change actually does anything but this line as it stands looks strictly less
correct.
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/5883#issuecomment-98597674
@davies @JoshRosen
---
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/5883#issuecomment-98598056
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/5883#issuecomment-98598086
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5883#issuecomment-98598511
[Test build #31732 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31732/consoleFull)
for PR 5883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5883#issuecomment-98626609
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5883#issuecomment-98626612
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/5883#issuecomment-98626586
[Test build #31732 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31732/consoleFull)
for PR 5883 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5883#issuecomment-98678863
Seems like it must be a typo, yeah.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5883
---
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/5558#issuecomment-94045004
[Test build #30488 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30488/consoleFull)
for PR 5558 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/5558#discussion_r28616483
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -519,7 +520,7 @@ def sort(self, *cols, **kwargs):
jcols = [jc if asc else jc.desc()
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5558#issuecomment-94045022
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5558#discussion_r28619523
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -519,7 +520,7 @@ def sort(self, *cols, **kwargs):
jcols = [jc if asc else jc.desc()
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/5558
Minor fix to SPARK-6958: Improve Python docstring for DataFrame.sort.
As a follow up PR to #5544.
cc @davies
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5558#issuecomment-94023259
[Test build #30488 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30488/consoleFull)
for PR 5558 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/5558#discussion_r28620686
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -519,7 +520,7 @@ def sort(self, *cols, **kwargs):
jcols = [jc if asc else jc.desc()
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5558#issuecomment-94059532
[Test build #30498 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30498/consoleFull)
for PR 5558 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/5558#discussion_r28621024
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -519,7 +520,7 @@ def sort(self, *cols, **kwargs):
jcols = [jc if asc else jc.desc()
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5558#discussion_r28623405
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -519,7 +520,7 @@ def sort(self, *cols, **kwargs):
jcols = [jc if asc else jc.desc()
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5558#discussion_r28625538
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -519,7 +520,7 @@ def sort(self, *cols, **kwargs):
jcols = [jc if asc else jc.desc()
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/5558#discussion_r28625392
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -519,7 +520,7 @@ def sort(self, *cols, **kwargs):
jcols = [jc if asc else jc.desc()
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5558
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/5558#issuecomment-94078338
LGTM.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5558#issuecomment-94078148
[Test build #30498 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30498/consoleFull)
for PR 5558 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5558#issuecomment-94078159
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/5558#discussion_r28631401
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -519,7 +520,7 @@ def sort(self, *cols, **kwargs):
jcols = [jc if asc else jc.desc()
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4936#issuecomment-77681480
[Test build #28365 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28365/consoleFull)
for PR 4936 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4936#issuecomment-77687597
Yes, clear typo fix, thank you.
---
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/4936
---
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 WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/4936
[Minor]fix the wrong description
Found it by accident. I'm not gonna file jira for this as it is a very tiny
fix.
You can merge this pull request into a Git repository by running:
$
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4936#issuecomment-77681785
Test FAILed.
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/4936#issuecomment-77684159
[Test build #28365 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28365/consoleFull)
for PR 4936 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4936#issuecomment-77684165
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4762
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/4762#issuecomment-76824082
Merged to master and 1.3
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/4762#issuecomment-76681887
CC @marmbrus
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/4762#issuecomment-76342273
I think this is a minor one. Does anyone know if the change is correct?
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4762#issuecomment-75926080
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4762#issuecomment-75928965
I don't know enough to be sure if the change is right, but, I suggest the
PR title be made more meaningful than fix document typo' since it will become
a commit message.
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/4762#issuecomment-75929446
@srowen Thanks. Using a more meaningful title now.
---
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/4762#issuecomment-75926075
[Test build #27945 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27945/consoleFull)
for PR 4762 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/4762
[Minor] Fix document type
It should be `true` instead of `false`?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/viirya/spark-1 doc_fix
101 - 200 of 391 matches
Mail list logo
