Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10865#issuecomment-173790014
cc @cloud-fan
---
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/10870#issuecomment-173796348
yeah, looks like it is.
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10870#issuecomment-173796866
Thank you! @cloud-fan @rxin @viirya .
Then, should we change the current conf name? The current name sounds like
covering both writing and reading.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10723#issuecomment-173800198
**[Test build #49897 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49897/consoleFull)**
for PR 10723 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173802247
**[Test build #49898 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49898/consoleFull)**
for PR 10829 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10648#issuecomment-173802223
**[Test build #49899 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49899/consoleFull)**
for PR 10648 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10873#issuecomment-173769038
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/10873#issuecomment-173769036
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/9532#issuecomment-173769068
**[Test build #49896 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49896/consoleFull)**
for PR 9532 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10762#discussion_r50497869
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicOperators.scala
---
@@ -164,11 +164,42 @@ case class Join(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173804717
**[Test build #49900 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49900/consoleFull)**
for PR 10829 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/10762#issuecomment-173804613
When the parser calls the constructor, how can we get the schema of tables?
We need schema to build project list and conditions.
---
If your project is set up for
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/10871#issuecomment-173768852
cc @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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10873#issuecomment-173768931
**[Test build #49895 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49895/consoleFull)**
for PR 10873 at commit
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/9532#issuecomment-173770249
@srowen This built locally.
---
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 ajbozarth commented on the pull request:
https://github.com/apache/spark/pull/10873#issuecomment-173785874
---
If your project
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10845#discussion_r50497168
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -462,6 +462,32 @@ object HiveTypeCoercion {
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10695#issuecomment-173787918
Thanks - I've merged this in master.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9532#issuecomment-173802601
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/10873#issuecomment-173775200
code wise this looks fine, do we have before/after screen shots handy?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-173787354
I will add this to the review queue. But to be honest this API is super
hard to design and I am not sure if there is an easy solution. The priority is
also not very high
Github user sameeragarwal commented on the pull request:
https://github.com/apache/spark/pull/10844#issuecomment-173787321
@hvanhovell added, 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10854#issuecomment-173794727
**[Test build #2433 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2433/consoleFull)**
for PR 10854 at commit
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173802481
@sun-rui Thanks for your comments. There is a ```cov``` implementation at
stats.R with different signature:
```R
setMethod("cov",
signature(x =
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173802435
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/10829#issuecomment-173802433
**[Test build #49898 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49898/consoleFull)**
for PR 10829 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9532#issuecomment-173802510
**[Test build #49896 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49896/consoleFull)**
for PR 9532 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173802437
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/10875
[SPARK-12961][Core] Prevent snappy-java memory leak
JIRA: https://issues.apache.org/jira/browse/SPARK-12961
To prevent memory leak in snappy-java, just call the method once and cache
the
GitHub user Wenpei opened a pull request:
https://github.com/apache/spark/pull/10874
[SPARK-5865] [WIP] [API DOC] Add doc warnings for methods that return local
data structures
@rxin @srowen
I work out note message for rdd.take function, please help to review.
If it's
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10874#issuecomment-173778315
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10870#discussion_r50495249
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/sources/BucketedWriteSuite.scala
---
@@ -183,4 +186,25 @@ class BucketedWriteSuite extends
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10762#discussion_r50497380
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/CheckAnalysis.scala
---
@@ -104,6 +105,9 @@ trait CheckAnalysis {
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10762#issuecomment-173789746
Actually now i think about it - maybe we should just have a constructor for
Join that the parser calls, and the constructor just creates a normal join with
the right
Github user andygrove commented on a diff in the pull request:
https://github.com/apache/spark/pull/10865#discussion_r50498238
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -406,7 +406,7 @@ object JavaTypeInference {
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10844#issuecomment-173796157
@sameeragarwal I just saw it. Thank you! I will do the code changes after
this is merged.
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9532#issuecomment-173802603
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/9946#issuecomment-173761688
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/9946#issuecomment-173761686
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/9946#issuecomment-173761532
**[Test build #49891 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49891/consoleFull)**
for PR 9946 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10871#issuecomment-173762361
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/10862
---
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 sun-rui commented on the pull request:
https://github.com/apache/spark/pull/10580#issuecomment-173772179
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10762#discussion_r50497736
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/SQLQuerySuite.scala
---
@@ -1463,4 +1463,24 @@ class SQLQuerySuite extends QueryTest
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/10807#issuecomment-173769284
@srowen it's good - I agree asking the caller to retry stop() or even put
it in a loop is too far off. It might happen when someone is running from
spark-shell or
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10870#issuecomment-173786234
I think the bucketing config should only impact read path, not write path?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10695
---
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 thomastechs commented on the pull request:
https://github.com/apache/spark/pull/10807#issuecomment-173808337
This fix would be executed in similar consistent way it has been fixed in
SparkContext.stop() .I think this is fine.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10845#issuecomment-173813686
**[Test build #49902 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49902/consoleFull)**
for PR 10845 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/10872#issuecomment-173813159
LGTM, merging this into master, 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
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10870#issuecomment-173815906
Yeah, I am learning your PR. @cloud-fan I am thinking if we should have
two functions for `getBucketSpec`? Something like `getBucketReadingSpec` and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10870#issuecomment-173824211
**[Test build #49907 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49907/consoleFull)**
for PR 10870 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10868#issuecomment-173829905
**[Test build #49912 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49912/consoleFull)**
for PR 10868 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10876#issuecomment-173830980
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/10876#issuecomment-173830979
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/10876#issuecomment-173830894
**[Test build #49909 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49909/consoleFull)**
for PR 10876 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173808613
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/10845#issuecomment-173819651
**[Test build #49902 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49902/consoleFull)**
for PR 10845 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10648#issuecomment-173819626
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/10648#issuecomment-173819628
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10854#discussion_r50505842
--- Diff: core/src/main/scala/org/apache/spark/rpc/netty/Dispatcher.scala
---
@@ -175,7 +175,7 @@ private[netty] class Dispatcher(nettyEnv: NettyRpcEnv)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10828#issuecomment-173825089
**[Test build #2434 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2434/consoleFull)**
for PR 10828 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10868#issuecomment-173829376
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10854#issuecomment-173829285
**[Test build #49911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49911/consoleFull)**
for PR 10854 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173835445
**[Test build #49913 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49913/consoleFull)**
for PR 10829 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10870#issuecomment-173817241
Yeah, that is a good idea! Will make a try
---
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/10723#issuecomment-173819276
**[Test build #49897 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49897/consoleFull)**
for PR 10723 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10723#issuecomment-173820489
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10876#issuecomment-173828115
**[Test build #49909 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49909/consoleFull)**
for PR 10876 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173808558
**[Test build #49900 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49900/consoleFull)**
for PR 10829 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173808612
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10870#issuecomment-173814981
No, it will impact write path:
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala#L466
and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10648#issuecomment-173819560
**[Test build #49899 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49899/consoleFull)**
for PR 10648 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10865#issuecomment-173820679
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10868#issuecomment-173821934
**[Test build #49904 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49904/consoleFull)**
for PR 10868 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10723#issuecomment-173821994
**[Test build #49905 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49905/consoleFull)**
for PR 10723 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10875#issuecomment-173806699
**[Test build #49901 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49901/consoleFull)**
for PR 10875 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10872
---
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/10563#issuecomment-173816915
**[Test build #49903 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49903/consoleFull)**
for PR 10563 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10870#issuecomment-173816599
I think this config should not impact write path logically, how about we
use `maybeBucketSpec` instead of `getBucketSpec` in write path?
---
If your project is set
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10723#issuecomment-173819378
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/10723#issuecomment-173819379
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/10829#issuecomment-173824949
@yanboliang, we can have different methods for a generic function. You can
try something like follows:
```
setGeneric("cov", function(x, ...)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10875#issuecomment-173824995
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/10875#issuecomment-173824996
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/10828#issuecomment-173825080
**[Test build #2435 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2435/consoleFull)**
for PR 10828 at commit
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/10876
[SPARK-12962] [SQL] [PySpark] PySpark support covar_samp and covar_pop
PySpark support ```covar_samp``` and ```covar_pop```.
cc @rxin @davies @marmbrus
You can merge this pull request
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10868#issuecomment-173827629
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/10868#issuecomment-173827621
**[Test build #49904 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49904/consoleFull)**
for PR 10868 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10868#issuecomment-173827628
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10854#issuecomment-173828649
> Test build #49860 has finished for PR 10854 at commit 39f21de.
>
> This patch fails from timeout after a configured wait of `250m`.
> This patch merges
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10845#issuecomment-173834979
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/10845#issuecomment-173834872
**[Test build #49906 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49906/consoleFull)**
for PR 10845 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10845#issuecomment-173834978
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/10845#issuecomment-173822992
**[Test build #49906 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49906/consoleFull)**
for PR 10845 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10875#issuecomment-173824900
**[Test build #49901 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49901/consoleFull)**
for PR 10875 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10563#issuecomment-173825705
**[Test build #49910 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49910/consoleFull)**
for PR 10563 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10854#issuecomment-173825728
**[Test build #49908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49908/consoleFull)**
for PR 10854 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10868#issuecomment-173677271
**[Test build #49879 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49879/consoleFull)**
for PR 10868 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10868#issuecomment-173677523
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
201 - 300 of 307 matches
Mail list logo
