Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8743
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168372683
Thanks - I've merged this.
---
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 ouyangshourui commented on the pull request:
https://github.com/apache/spark/pull/10549#issuecomment-168376381
thank you ,srowen .you can close this PR. I will argue this change is
necessary in the JIRA in SPARK-12601.
---
If your project is set up for it, you can reply
Github user ouyangshourui closed the pull request at:
https://github.com/apache/spark/pull/10549
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10546#issuecomment-168381491
@datafarmer go ahead and update the title here and consider updating the PR
itself per above.
---
If your project is set up for it, you can reply to this email and
GitHub user hvanhovell opened a pull request:
https://github.com/apache/spark/pull/10553
[SPARK-12421][SQL] Prevent Internal/External row from exposing state.
It is currently possible to change the values of the supposedly immutable
```GenericRow``` and ```GenericInternalRow```
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10549#issuecomment-168375947
Please read
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark Do you
mind closing this PR or fixing it? though I think you first need to argue
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/10552
[SPARK-12603] [MLlib] PySpark MLlib GaussianMixtureModel should support
single instance predict/predictSoft
PySpark MLlib GaussianMixtureModel should support single instance
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10552#issuecomment-168378126
**[Test build #48580 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48580/consoleFull)**
for PR 10552 at commit
Github user srowen closed the pull request at:
https://github.com/apache/spark/pull/10446
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10546#issuecomment-168390342
@datafarmer I've just seconds ago merged a change that replaces these
deprecated calls, since we can assume Hadoop 2.2+ now. Yes, isDirectory is
correct now.
---
If
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10446#issuecomment-168390287
Merged to 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 not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10547#issuecomment-168372795
**[Test build #2296 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2296/consoleFull)**
for PR 10547 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10552#issuecomment-168379412
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 guoxu1231 commented on a diff in the pull request:
https://github.com/apache/spark/pull/10464#discussion_r48684054
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/SocketInputDStream.scala
---
@@ -51,29 +51,44 @@ class SocketReceiver[T: ClassTag](
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/7385#issuecomment-168384426
@zsxwing @JoshRosen Does the comment need attention since the pr is closed,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10553#issuecomment-168390480
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/10553#issuecomment-168390446
**[Test build #48581 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48581/consoleFull)**
for PR 10553 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10554#issuecomment-168391002
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/10554#issuecomment-168391003
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/10555
[Minor][SQL] Replace logger name
This is very minor update. @rxin Please see if it is proper for you. If
not, I will close it. Thanks.
You can merge this pull request into a Git repository by
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10555#issuecomment-168396939
LGTM - missed that one.
---
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/10551#issuecomment-168372904
**[Test build #48577 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48577/consoleFull)**
for PR 10551 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168372938
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/10551#issuecomment-168372937
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/10547#issuecomment-168375242
**[Test build #2296 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2296/consoleFull)**
for PR 10547 at commit
Github user datafarmer commented on the pull request:
https://github.com/apache/spark/pull/10546#issuecomment-168389034
@srowen I'll update the PR per your changes. BTW, the FileStatus method
isDir is deprecated. Should I change it to isDirectory, or is that something
for another
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10553#issuecomment-168392086
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/10553#issuecomment-168391748
**[Test build #48582 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48582/consoleFull)**
for PR 10553 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10548#issuecomment-168375899
I generally favor removing deprecated methods in a 2.x release. I wanted to
ask what your (and others') opinions are on it, since there's some argument for
possibly
Github user guoxu1231 commented on a diff in the pull request:
https://github.com/apache/spark/pull/10464#discussion_r48684056
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/SocketInputDStream.scala
---
@@ -51,29 +51,44 @@ class SocketReceiver[T: ClassTag](
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168384367
@liancheng this looks cool!
I was wondering why we are bound to SQL? Is this because of Hive? I was
thinking of the following, we could also store the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10553#issuecomment-168384349
**[Test build #48582 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48582/consoleFull)**
for PR 10553 at commit
Github user Cazen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10497#discussion_r48684498
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/json/JSONOptions.scala
---
@@ -59,6 +62,8 @@ object JSONOptions {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10554#issuecomment-168393617
**[Test build #2297 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2297/consoleFull)**
for PR 10554 at commit
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/10544#issuecomment-168376268
@rxin ```transformFunc``` is not a public API, but I think your PR is more
concise and I will close my PR.
---
If your project is set up for it, you can reply to
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10492#issuecomment-168381598
@JoshRosen are you OK with the reasoning above?
@BrianLondon sorry but the style checker doesn't like the white space on
the blank line you added to trigger tests
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10553#issuecomment-168383990
**[Test build #48581 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48581/consoleFull)**
for PR 10553 at commit
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/10554
[SPARK-12604] [CORE] Java count(AprroxDistinct)ByKey methods return Scala
Long not Java
Change Java countByKey, countApproxDistinctByKey return types to use Java
Long, not Scala; update similar
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168373130
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/10551#issuecomment-168373133
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/10551#issuecomment-168373107
**[Test build #48578 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48578/consoleFull)**
for PR 10551 at commit
Github user yanboliang closed the pull request at:
https://github.com/apache/spark/pull/10544
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10552#issuecomment-168379413
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/10552#issuecomment-168379387
**[Test build #48580 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48580/consoleFull)**
for PR 10552 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10553#issuecomment-168390479
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/10553#issuecomment-168392090
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10526#issuecomment-168395739
@yucai can you update accordingly?
---
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/10553#issuecomment-168395737
**[Test build #48584 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48584/consoleFull)**
for PR 10553 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10555#issuecomment-168405571
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/10555#issuecomment-168405569
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/10556#issuecomment-168409759
**[Test build #48586 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48586/consoleFull)**
for PR 10556 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10557#issuecomment-168426136
**[Test build #48587 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48587/consoleFull)**
for PR 10557 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10557#issuecomment-168426184
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/10557#issuecomment-168426183
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/10555#issuecomment-168397196
**[Test build #48585 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48585/consoleFull)**
for PR 10555 at commit
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10555#issuecomment-168399954
@viirya I am working on a PR to remove all Hive dependencies from the
parser. In order to do this, I am also touching the ```ParseDriver```. That
might supercede
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10555#issuecomment-168405533
**[Test build #48585 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48585/consoleFull)**
for PR 10555 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/10556
[SPARK-12605] [SQL] [WIP] Pushing Join Predicates Through Union All
When selectivity of Join predicates is high, we can push join through union
all for performance improvement.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10553#issuecomment-168401275
**[Test build #48584 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48584/consoleFull)**
for PR 10553 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10553#issuecomment-168401330
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/10553#issuecomment-168401328
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/10554#issuecomment-168400458
**[Test build #2297 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2297/consoleFull)**
for PR 10554 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/10557
[SPARK-12578][SQL] Distinct should not be silently ignored when used in an
aggregate function with OVER clause
JIRA: https://issues.apache.org/jira/browse/SPARK-12578
Slightly update to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10557#issuecomment-168416561
**[Test build #48587 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48587/consoleFull)**
for PR 10557 at commit
Github user viirya closed the pull request at:
https://github.com/apache/spark/pull/10555
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/10555#issuecomment-168401446
Ok. No problem. Close this now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user thomastechs commented on the pull request:
https://github.com/apache/spark/pull/10529#issuecomment-168407320
@SparkQA , @rxin The changes are done to fix the unit test failure. Could
you please initiate a test build?
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10556#issuecomment-168416991
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/10556#issuecomment-168416990
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/10556#issuecomment-168416841
**[Test build #48586 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48586/consoleFull)**
for PR 10556 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10534#discussion_r48687981
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -81,6 +81,7 @@ class StreamingContextSuite extends
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10519#issuecomment-168435471
I'd appreciate any feedback on how we can/should test this change and
prevent this behavior from regressing in the future.
---
If your project is set up for it, you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168435937
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/10551#issuecomment-168435938
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/10534#issuecomment-168439939
**[Test build #48592 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48592/consoleFull)**
for PR 10534 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10534#issuecomment-168439980
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/10534#issuecomment-168439979
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/10558#issuecomment-168439965
**[Test build #48594 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48594/consoleFull)**
for PR 10558 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168440612
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/10551#issuecomment-168440613
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/10551#issuecomment-168440559
**[Test build #48593 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48593/consoleFull)**
for PR 10551 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10558#issuecomment-168441964
**[Test build #2298 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2298/consoleFull)**
for PR 10558 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10558#issuecomment-168449633
**[Test build #2298 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2298/consoleFull)**
for PR 10558 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168428246
**[Test build #48588 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48588/consoleFull)**
for PR 10551 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168435788
**[Test build #48593 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48593/consoleFull)**
for PR 10551 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10558#issuecomment-168434910
**[Test build #48589 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48589/consoleFull)**
for PR 10558 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10558#issuecomment-168435305
Test failure was due to Python 3.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10534#issuecomment-168435869
**[Test build #48592 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48592/consoleFull)**
for PR 10534 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10558#issuecomment-168435906
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/10558#issuecomment-168435904
**[Test build #48591 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48591/consoleFull)**
for PR 10558 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10558#issuecomment-168435907
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/10558#issuecomment-168435836
**[Test build #48591 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48591/consoleFull)**
for PR 10558 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168435871
**[Test build #48588 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48588/consoleFull)**
for PR 10551 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10534#issuecomment-168440019
**[Test build #48590 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48590/consoleFull)**
for PR 10534 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10534#issuecomment-168440046
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/10534#issuecomment-168440044
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 JoshRosen opened a pull request:
https://github.com/apache/spark/pull/10558
[SPARK-10359][PROJECT-INFRA] Use a more random suffix in
dev/test-dependencies.sh
This patch aims to fix another potential source of flakiness in the
`dev/test-dependencies.sh` script.
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10558#issuecomment-168432407
/cc @rxin
---
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10534#discussion_r48688012
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -291,17 +289,10 @@ private[spark] class MapOutputTrackerMaster(conf:
1 - 100 of 142 matches
Mail list logo
