Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112074260
[Test build #34940 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34940/console)
for PR 6762 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112074271
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 suyanNone commented on the pull request:
https://github.com/apache/spark/pull/6586#issuecomment-112051808
@JoshRosen
The netty direct buffer leak problem fix on Netty-4.0.29-Final, but it is
not release official yet.
Although I also not sure that patch is
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/6586#issuecomment-112055404
and I also think it may be more better to de-allocate direct Buffer while
we send chunkFetchSuccess to requester.
I not sure I right or not,
NioManagedBuffer
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/6826#discussion_r32416752
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -425,6 +425,11 @@ private[spark] object PythonRDD extends Logging {
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6774#discussion_r32416734
--- Diff: core/src/main/scala/org/apache/spark/SecurityManager.scala ---
@@ -365,10 +365,12 @@ private[spark] class SecurityManager(sparkConf:
SparkConf)
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6825#discussion_r32422035
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/arithmetic.scala
---
@@ -341,9 +341,20 @@ case class MaxOf(left:
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-112063658
This is built into the assembly though, right?
No. Spark Flume Sink does not assemble the dependencies. Actually, now we
don't have an assembly jar for Flume.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-112065369
[Test build #34937 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34937/consoleFull)
for PR 6826 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-112080610
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/6829#issuecomment-112040285
[Test build #34936 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34936/consoleFull)
for PR 6829 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-112058266
This is built into the assembly though, right?
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/6826#discussion_r32416715
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -425,6 +425,11 @@ private[spark] object PythonRDD extends Logging {
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-112071017
OK but surely it's easier to make an assembly target than tell people
they have to piece together the dependencies and keep updating docs about it?
ping @tdas
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112072097
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/6823#issuecomment-112072116
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/6762#issuecomment-112072115
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/6823#issuecomment-112072092
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/6829#issuecomment-112080561
[Test build #34936 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34936/console)
for PR 6829 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/6825#issuecomment-112081358
retest it 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 zsxwing opened a pull request:
https://github.com/apache/spark/pull/6830
[SPARK-8378][Streaming]Add the Python API for Flume
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zsxwing/spark flume-python
Alternatively
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-112098302
[Test build #34942 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34942/consoleFull)
for PR 6830 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-112110192
[Test build #34944 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34944/consoleFull)
for PR 6686 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112119473
[Test build #34941 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34941/console)
for PR 6762 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112119521
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/6826#issuecomment-112093726
/cc @davies
---
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/6686#issuecomment-112099273
[Test build #34943 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34943/consoleFull)
for PR 6686 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6807
---
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/6262#issuecomment-112117868
[Test build #34945 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34945/consoleFull)
for PR 6262 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/6774#issuecomment-112118402
Actually, this is the kind of patch I wanted to preempt with my
previous patch, because I think eventually when we support per-app secrets in
standalone mode
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-112119135
The tests pass because the `createDataFrame` call only fails in the YARN
cluster mode and we don't have tests for SparkR in the YarnSuite (Actually this
deserves a new
GitHub user lianhuiwang opened a pull request:
https://github.com/apache/spark/pull/6831
[SPARK][Minor]reuse-typeConvert when convert Seq[Row] to CatalystType
reuse-typeConvert when convert Seq[Row] to CatalystType
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/6831#issuecomment-112121503
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/6831#issuecomment-112121566
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/6762#issuecomment-112086486
[Test build #34941 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34941/consoleFull)
for PR 6762 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/6830#discussion_r32428495
--- Diff: external/flume-assembly/pom.xml ---
@@ -0,0 +1,134 @@
+?xml version=1.0 encoding=UTF-8?
+!--
+ ~ Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-112099204
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/6826#issuecomment-112099091
[Test build #34937 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34937/console)
for PR 6826 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-112098983
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/6823#issuecomment-112105235
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/6823#issuecomment-112105166
[Test build #34939 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34939/console)
for PR 6823 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-112117430
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/6262#issuecomment-112117358
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 squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/6752#discussion_r32435583
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -1183,6 +1187,29 @@ object Client extends Logging {
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6826#issuecomment-112096232
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/5533#issuecomment-112098723
@hotienvu could you open a JIRA and describe more details? Such as the
error information and the invalid link?
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-112098935
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6671#discussion_r32435228
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -460,7 +460,9 @@ private[deploy] class SparkSubmitArguments(args:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-112099705
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/6686#issuecomment-112099702
[Test build #34943 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34943/console)
for PR 6686 at commit
Github user bplaster commented on the pull request:
https://github.com/apache/spark/pull/5541#issuecomment-112112402
This should probably be noted here:
https://spark.apache.org/docs/latest/api/scala/index.html#org.apache.spark.sql.DataFrame
---
If your project is set up for it, you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-112118518
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/6262#issuecomment-112118514
[Test build #34945 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34945/console)
for PR 6262 at commit
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/6752#discussion_r32436913
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -1183,6 +1187,29 @@ object Client extends Logging {
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6827#discussion_r32437068
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -160,7 +160,7 @@ private[history] class FsHistoryProvider(conf:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112084997
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/6762#issuecomment-112084934
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6752#discussion_r32436071
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -1183,6 +1187,29 @@ object Client extends Logging {
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6824#issuecomment-112119776
As mentioned in the JIRA, we should also do this for the R API
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-112120882
@jerryshao The `res.map { r =` version would be considered idiomatic Scala
style, not weird. In this case, there's not a lot of reason to prefer one
style over the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-112097150
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/6830#issuecomment-112097188
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/6686#issuecomment-112108881
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/6686#issuecomment-112108953
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 ehnalis commented on a diff in the pull request:
https://github.com/apache/spark/pull/6671#discussion_r32433381
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -460,7 +460,9 @@ private[deploy] class SparkSubmitArguments(args:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6783#issuecomment-111948376
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/6783#issuecomment-111948347
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/6821#issuecomment-111949069
[Test build #34911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34911/consoleFull)
for PR 6821 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6783#issuecomment-111949121
[Test build #34912 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34912/consoleFull)
for PR 6783 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6821#issuecomment-111949329
[Test build #34911 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34911/console)
for PR 6821 at commit
Github user shimingfei commented on the pull request:
https://github.com/apache/spark/pull/6702#issuecomment-111949564
ping
---
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/5733#issuecomment-111949566
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/5733#issuecomment-111949553
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/6821#issuecomment-111949340
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/5733#issuecomment-111949782
[Test build #34913 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34913/consoleFull)
for PR 5733 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6780#discussion_r32394261
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -160,17 +166,22 @@ case class TakeOrdered(limit: Int,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6721#issuecomment-111950220
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/6721#issuecomment-111950169
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/6721#issuecomment-111951645
[Test build #34914 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34914/consoleFull)
for PR 6721 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6779#issuecomment-112258188
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/6779#issuecomment-112258180
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/6833#issuecomment-112259097
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 jeanlyn opened a pull request:
https://github.com/apache/spark/pull/6833
[SPARK-8379][SQL]avoid speculative tasks write to the same file
The issue link
[SPARK-8379](https://issues.apache.org/jira/browse/SPARK-8379)
Currently,when we insert data to the dynamic
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6679#issuecomment-112263664
[Test build #34962 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34962/console)
for PR 6679 at commit
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6775#discussion_r32487610
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -914,6 +914,42 @@ object functions {
def ceil(columnName: String):
Github user jeanlyn commented on a diff in the pull request:
https://github.com/apache/spark/pull/6833#discussion_r32492419
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/InsertIntoHiveTable.scala
---
@@ -197,7 +197,6 @@ case class InsertIntoHiveTable(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6836#issuecomment-112303723
[Test build #34972 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34972/consoleFull)
for PR 6836 at commit
Github user zhichao-li commented on the pull request:
https://github.com/apache/spark/pull/6783#issuecomment-112303755
@adrian-wang @chenghao-intel , wondering what type of api we should reserve
regarding to this kind of api ` def pmod(leftName: String, r: Integer): Column`
? I
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112249235
@JoshRosen yes, I have removed all uses of
CatalystTypeConverters.convertToCatalyst and also removed this method.
---
If your project is set up for it, you can
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6827#discussion_r32486202
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/FsHistoryProviderSuite.scala
---
@@ -218,6 +223,18 @@ class FsHistoryProviderSuite extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6679#issuecomment-112263687
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/6804#issuecomment-112263921
[Test build #916 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/916/consoleFull)
for PR 6804 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6825#issuecomment-112266153
@cloud-fan There are some changes related to Max/Min in #6726 , is it
useful for you? It will be good if you could merge them here.
---
If your project is set up for
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/6331#issuecomment-112265955
cc @jkbradley
---
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 holdenk closed the pull request at:
https://github.com/apache/spark/pull/6771
---
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 adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/6783#issuecomment-112269008
LGTM except the full type APIs
---
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/6460#issuecomment-112270239
[Test build #34968 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34968/consoleFull)
for PR 6460 at commit
Github user coderxiang commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-112271606
@dbtsai @jkbradley finished the Java and Python sample code.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-112273021
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 kanzhang commented on the pull request:
https://github.com/apache/spark/pull/6774#issuecomment-112272884
And I get what you are saying all along. :)
---
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
101 - 200 of 482 matches
Mail list logo
