Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10488#issuecomment-167834296
Can you update the pr? Once it passes jenkins, I will merge it. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167842481
**[Test build #48417 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48417/consoleFull)**
for PR 10509 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167847055
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user BenFradet commented on the pull request:
https://github.com/apache/spark/pull/10453#issuecomment-167848381
I have a few comments on phrasing but otherwise it lgtm
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10077#issuecomment-167848248
Closing this for now; this is blocked on an investigation into custom log
appenders in tests in order to fix the log interleaving problems, as well as an
Github user BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10453#discussion_r48559339
--- Diff: docs/streaming-programming-guide.md ---
@@ -2029,6 +2029,11 @@ If the data is being received by the receivers
faster than what can be processed
Github user JoshRosen closed the pull request at:
https://github.com/apache/spark/pull/10077
---
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 BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10453#discussion_r48559275
--- Diff: docs/configuration.md ---
@@ -1600,6 +1600,33 @@ Apart from these, the following properties are also
available, and may be useful
How
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10498#issuecomment-167823882
**[Test build #48415 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48415/consoleFull)**
for PR 10498 at commit
Github user radekg commented on the pull request:
https://github.com/apache/spark/pull/9608#issuecomment-167826085
I have 3 tests failing locally but I don't think these are related to my
changes. `scalastyle` seems to be ok now. Failing tests:
```
- launch simple
Github user kiszk commented on the pull request:
https://github.com/apache/spark/pull/10488#issuecomment-167848836
@yhuai, do you mean that I would update all of the string concatenation in
@ExpressionDescription by using multi-line string literals rather than only the
original one?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10506#issuecomment-167820998
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/10506#issuecomment-167821001
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/10498#issuecomment-167843318
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/10498#issuecomment-167843317
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/10498#issuecomment-167843065
**[Test build #48415 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48415/consoleFull)**
for PR 10498 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167848994
**[Test build #48420 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48420/consoleFull)**
for PR 10509 at commit
Github user blbradley commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-167848940
@dragos Where can you see that fine-grained mode is slated for removal? All
I see is #9795.
---
If your project is set up for it, you can reply to this email and
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10507#issuecomment-167856135
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10488#issuecomment-167834026
@kiszk Thank you for the investigation. Yeah, let's use multi-line string
literals. If we have to have a line with more than 100 characters, let's use
`// scalastyle:off
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167847328
**[Test build #48419 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48419/consoleFull)**
for PR 10509 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10453#discussion_r48559444
--- Diff: docs/configuration.md ---
@@ -1600,6 +1600,33 @@ Apart from these, the following properties are also
available, and may be useful
How
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167850051
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/10509#issuecomment-167850043
**[Test build #48420 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48420/consoleFull)**
for PR 10509 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167850053
Test FAILed.
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/10488
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10442#issuecomment-167855574
Also, I just noticed this is opened against the wrong branch. Please close
this PR and re-open it against master if we do decide to continue work on this
issue.
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/6935#discussion_r48548650
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/ApplicationCacheSuite.scala
---
@@ -0,0 +1,476 @@
+/*
+ * Licensed to the Apache
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10506#issuecomment-167820776
**[Test build #48413 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48413/consoleFull)**
for PR 10506 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10502#issuecomment-167835640
@HyukjinKwon Thank you for the PR? Can you post some benchmarking results
(with your testing code)? It will be good to have these numbers to help others
understand if it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167843425
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/10509#issuecomment-167843416
**[Test build #48417 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48417/consoleFull)**
for PR 10509 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167843424
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 hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167843520
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10451#discussion_r48558035
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -153,6 +153,17 @@ object SetOperationPushDown extends
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10451#issuecomment-167845210
Thanks for working on this. I think its getting pretty close. A few minor
cleanups that might be nice:
- I think we should consider pulling all the Limit rules
Github user BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10453#discussion_r48559015
--- Diff: docs/configuration.md ---
@@ -1600,6 +1600,33 @@ Apart from these, the following properties are also
available, and may be useful
How
Github user BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10453#discussion_r48558980
--- Diff: docs/configuration.md ---
@@ -1600,6 +1600,33 @@ Apart from these, the following properties are also
available, and may be useful
How
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/10421#discussion_r48562209
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/GenerateUnsafeRowJoiner.scala
---
@@ -171,7 +171,7 @@ object
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10507#issuecomment-167857621
@JerryLead I commented on the JIRA on why I don't think it's an issue.
Let's move the discussion there.
---
If your project is set up for it, you can reply to this
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167836899
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167846349
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/10509#issuecomment-167846350
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10453#discussion_r48559086
--- Diff: docs/configuration.md ---
@@ -1600,6 +1600,33 @@ Apart from these, the following properties are also
available, and may be useful
How
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10488#issuecomment-167849606
Let me merge this one first to fix the spark master maven snapshot. Then,
can you create another jira to update other places?
---
If your project is set up for it, you
Github user kiszk commented on the pull request:
https://github.com/apache/spark/pull/10488#issuecomment-167853136
I see. I will create another JIRA entry to update other usages.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-167855990
What first two days of work are you referring to? The problem is we just
can't use Kryo for serializing task results because there might be unregistered
classes.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9608#issuecomment-167826650
**[Test build #48416 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48416/consoleFull)**
for PR 9608 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/10435#discussion_r48554681
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/misc.scala
---
@@ -176,3 +179,223 @@ case class Crc32(child: Expression)
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167847029
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167847052
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/9608#issuecomment-167847920
**[Test build #48416 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48416/consoleFull)**
for PR 9608 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9608#issuecomment-167848079
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/9608#issuecomment-167848076
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 BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10453#discussion_r48559209
--- Diff: docs/configuration.md ---
@@ -1600,6 +1600,33 @@ Apart from these, the following properties are also
available, and may be useful
How
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/10421#issuecomment-167855300
@rxin I had finished the refactoring long time ago.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10510#issuecomment-167899182
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/10509#issuecomment-167900502
**[Test build #48430 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48430/consoleFull)**
for PR 10509 at commit
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167901239
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167901126
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/10509#issuecomment-167901129
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10451#issuecomment-167902518
After rethinking the `Limit` push-down rules, we are unable to push Limit
through any operator that could change the values or the number of rows. Thus,
so far, the
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/10514#issuecomment-167902559
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 gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/10451#discussion_r48581020
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -80,6 +81,33 @@ abstract class Optimizer extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10514#issuecomment-167905088
**[Test build #48429 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48429/consoleFull)**
for PR 10514 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10514#issuecomment-167905122
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/10514#issuecomment-167905123
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/10516
[SPARK-12568] [SQL] Add BINARY to Encoders
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark datasetCleanup
Alternatively you
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10446#discussion_r48581372
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/WriterContainer.scala
---
@@ -24,10 +24,9 @@ import
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10446#discussion_r48581350
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/SqlNewHadoopRDD.scala
---
@@ -26,10 +26,10 @@ import
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/10446#issuecomment-167907581
LGTM; there's at least one extra possible cleanup, but feel free to punt on
that one.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10514#issuecomment-167912484
**[Test build #48438 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48438/consoleFull)**
for PR 10514 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10504
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8960#issuecomment-167914321
@rahulpalamuttam Sorry for the delay in reviewing! How would you feel
about updating the implementation in Breeze, rather than in Spark? I expect
you could use much
Github user xguo27 commented on the pull request:
https://github.com/apache/spark/pull/10515#issuecomment-167915743
@marmbrus Thanks Michael for your feedback!
Looks like the 'value' is to give the single string column a arbitrary
name. Current implementation strips schema
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10435#issuecomment-167918200
**[Test build #48442 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48442/consoleFull)**
for PR 10435 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-16798
I'm going to merge this pull request given the size.
@hvanhovell please submit follow up prs to address the todos. Thanks!
---
If your project is set up for
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/10514
[SPARK-12511][PySpark][Streaming]Make sure TransformFunctionSerializer is
created only once
Although SPARK-12511 is because of an issue in Py4j that
PythonProxyHandler.finalize blocks forever, we
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10510#issuecomment-167899086
**[Test build #48423 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48423/consoleFull)**
for PR 10510 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4027#issuecomment-167899082
> Earlier, you had also suggested offering an option for the amount of
memory per executor. Is that still valid in your proposal?
What do you mean? You can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10510#issuecomment-167899180
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/10514#issuecomment-167900273
**[Test build #48429 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48429/consoleFull)**
for PR 10514 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10451#discussion_r48578529
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -69,6 +73,33 @@ object DefaultOptimizer extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10511#issuecomment-167901091
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/10511#issuecomment-167901090
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/10511#issuecomment-167901009
**[Test build #48432 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48432/consoleFull)**
for PR 10511 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10511#issuecomment-167901053
**[Test build #48425 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48425/consoleFull)**
for PR 10511 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10509#issuecomment-167901123
**[Test build #48430 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48430/consoleFull)**
for PR 10509 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10453#issuecomment-167902755
**[Test build #48436 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48436/consoleFull)**
for PR 10453 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10461#issuecomment-167906816
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10446#discussion_r48581268
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/EventLoggingListener.scala ---
@@ -97,7 +97,7 @@ private[spark] class EventLoggingListener(
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10451#discussion_r48581249
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/LogicalPlan.scala
---
@@ -91,6 +91,11 @@ abstract class LogicalPlan
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10461#issuecomment-167906817
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/10517#issuecomment-167910392
**[Test build #48439 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48439/consoleFull)**
for PR 10517 at commit
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/6360#issuecomment-167912850
Thanks @vanzin, my fault, I specify the hdfs location using hostname, while
it is ip address in core-site.xml (anyway, maybe we can improve it here)
---
If your project
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/10451#discussion_r48582039
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -80,6 +81,33 @@ abstract class Optimizer extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10511#issuecomment-167914257
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/10511#issuecomment-167914254
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/10511#issuecomment-167914227
**[Test build #48432 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48432/consoleFull)**
for PR 10511 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10459#issuecomment-167914770
CC @vanzin @andrewor14
---
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
1 - 100 of 485 matches
Mail list logo
