Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8794#issuecomment-140987447
[Test build #42581 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42581/consoleFull)
for PR 8794 at commit
[`1cc1b14`](https://gith
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/8662#issuecomment-140989401
Here are some benchmark with different approaches:
```
Without fix:
Number of udfs: 0 - 0.142887830734
Number of udfs: 1 - 0.948309898376
Number of udfs
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8665#issuecomment-140989949
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8665#issuecomment-140989979
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/8665#issuecomment-140990352
[Test build #42582 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42582/consoleFull)
for PR 8665 at commit
[`f1ce652`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140990611
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140990635
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/8688#issuecomment-140991676
[Test build #42583 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42583/consoleFull)
for PR 8688 at commit
[`6b51692`](https://gith
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8554#issuecomment-140991974
Sure! I'll check 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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140992127
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140992118
[Test build #42583 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42583/console)
for PR 8688 at commit
[`6b51692`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140992124
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140992962
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140992970
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/8665#issuecomment-140993216
[Test build #42582 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42582/console)
for PR 8665 at commit
[`f1ce652`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8665#issuecomment-140993321
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/8665#issuecomment-140993322
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8662#issuecomment-140993762
If I'm reading it correctly, this is not "appends all the rows into an
array when compute() is called for the first time, then pull and remove the
rows when compute() is ca
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8684#issuecomment-140993868
All right. I have rebased this PR with the master branch.
---
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 yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8685#issuecomment-140994118
@noel-smith thank you for reviewing 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 d
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8662#issuecomment-140994101
Actually never mind - it does. This seems a lot more complicated still - we
would need to handle spilling, and then in that case it would strictly be
slower due to the unne
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140994092
[Test build #42584 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42584/consoleFull)
for PR 8688 at commit
[`c52e35d`](https://gith
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8689#issuecomment-140994215
@noel-smith thanks for the review.
---
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 n
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8684#issuecomment-140994609
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8684#issuecomment-140994592
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8684#issuecomment-140994959
[Test build #42585 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42585/consoleFull)
for PR 8684 at commit
[`2524a40`](https://gith
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8784
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-140995258
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 this f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-140995239
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 have thi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-140995503
[Test build #42586 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42586/consoleFull)
for PR 8690 at commit
[`970ae03`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8631#issuecomment-140996512
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8631#issuecomment-140996513
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8631#issuecomment-140996440
[Test build #42579 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42579/console)
for PR 8631 at commit
[`3f98247`](https://github.
GitHub user jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/8795
[MINOR][DOCS] Fixes markup so code is properly formatted
* Backticks are processed properly in Spark Properties table
* Removed unnecessary spaces
* See
http://people.apache.org/~pwen
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8795#issuecomment-140998628
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 pr
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8616#issuecomment-140999032
cc @davies - this looks good to me?
---
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 litao-buptsse commented on the pull request:
https://github.com/apache/spark/pull/4380#issuecomment-140999722
@scwf @liancheng Is there any plan to merge this PR to branch-1.5 recently?
I think this feature is pretty useful.
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-141000373
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-141000349
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 h
Github user ericl commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-141000851
@mengxr made the requested changes. I found it simpler to keep
`numFeatures` in combination with an array of offsets instead of just the
cumulative count though.
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-141001187
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-141001217
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/7987#issuecomment-141004752
[Test build #42588 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42588/consoleFull)
for PR 7987 at commit
[`09cba2c`](https://gith
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8662#issuecomment-141004821
OK I finally understood what's going on here. If I understand your
intention correctly, you are assuming:
1. The 1st read goes into Python
2. The 2nd read can k
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-141005114
@noel-smith @mengxr I have merged this PR with master and have added the
version info. to MultilayerPerceptronClassifier and
MultilayerPerceptronClassificationModel whic
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/8796
[SPARK-10642][PySpark] Fix crash when calling rdd.lookup() on tuple keys
JIRA: https://issues.apache.org/jira/browse/SPARK-10642
When calling `rdd.lookup()` on a RDD with tuple keys, `portabl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-141005165
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8796#issuecomment-141005177
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8668#issuecomment-141005169
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-141005178
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8796#issuecomment-141005161
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-141005176
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7987#issuecomment-141005175
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8668#issuecomment-141005189
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/8796#issuecomment-141005247
[Test build #42589 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42589/consoleFull)
for PR 8796 at commit
[`1eac461`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8668#issuecomment-141005574
[Test build #42591 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42591/consoleFull)
for PR 8668 at commit
[`cf56d21`](https://gith
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8796#discussion_r39721951
--- Diff: python/pyspark/rdd.py ---
@@ -84,7 +84,7 @@ def portable_hash(x):
h ^= len(x)
if h == -1:
h = -2
-
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-141005722
[Test build #42590 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42590/consoleFull)
for PR 8690 at commit
[`29950fd`](https://gith
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8662#issuecomment-141005883
BTW with all of these - I'm starting to think we should just do a quick fix
for 1.5.1, and then for 1.6 we would need to rewrite a lot of these in order to
use local iterat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8668#issuecomment-141006215
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8668#issuecomment-141006211
[Test build #42591 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42591/console)
for PR 8668 at commit
[`cf56d21`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8668#issuecomment-141006216
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8791#issuecomment-141006254
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7853#issuecomment-141006259
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8791#issuecomment-141006287
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7853#issuecomment-141006322
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/8791#issuecomment-141006583
[Test build #42592 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42592/consoleFull)
for PR 8791 at commit
[`fd0d435`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7853#issuecomment-141007767
[Test build #42593 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42593/consoleFull)
for PR 7853 at commit
[`9be133c`](https://gith
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/8668#issuecomment-141007880
@vanzin I try this way, 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 doe
Github user taishi-oss commented on the pull request:
https://github.com/apache/spark/pull/8534#issuecomment-141008317
I think DecisionTreeClassifer.copy is introduced in v1.5.0.
but, This method is brought into v.1.4.1 using "git-cherry-pick".
So "git blames" says v.1.5.0 but "
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8692#issuecomment-141012139
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8796#issuecomment-141012113
[Test build #42589 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42589/console)
for PR 8796 at commit
[`1eac461`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8692#issuecomment-141012190
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8691#issuecomment-141012157
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8796#issuecomment-141012221
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8691#issuecomment-141012229
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8796#issuecomment-141012223
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8691#issuecomment-141012823
[Test build #42595 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42595/consoleFull)
for PR 8691 at commit
[`8b1e2fc`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-141012759
[Test build #42590 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42590/console)
for PR 8690 at commit
[`29950fd`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-141013030
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8690#issuecomment-141013027
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/8791#issuecomment-141013097
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8791#issuecomment-141012988
[Test build #42592 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42592/console)
for PR 8791 at commit
[`fd0d435`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8791#issuecomment-141013101
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8693#issuecomment-141015283
@noel-smith I have merged this PR with master and have fixed them which you
reviewed. Could you check it please?
---
If your project is set up for it, you can reply to
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/8796#issuecomment-141015069
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 fea
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8692#issuecomment-141015686
[Test build #42594 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42594/consoleFull)
for PR 8692 at commit
[`d719dc3`](https://gith
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/8796#discussion_r39724065
--- Diff: python/pyspark/rdd.py ---
@@ -84,7 +84,7 @@ def portable_hash(x):
h ^= len(x)
if h == -1:
h = -2
-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8693#issuecomment-141017098
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8694#issuecomment-141017081
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8796#issuecomment-141017113
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8796#issuecomment-141017064
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8694#issuecomment-141017130
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8693#issuecomment-141017129
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/8796#issuecomment-141017205
[Test build #42596 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42596/consoleFull)
for PR 8796 at commit
[`1eac461`](https://gith
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8695#issuecomment-141017724
Close this PR because those are non-public API.
---
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 p
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8693#issuecomment-141017698
[Test build #42598 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42598/consoleFull)
for PR 8693 at commit
[`acdc52e`](https://gith
Github user yu-iskw closed the pull request at:
https://github.com/apache/spark/pull/8695
---
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 ena
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8791#issuecomment-141018026
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8791#issuecomment-141018006
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 h
1 - 100 of 678 matches
Mail list logo
