Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10678#issuecomment-171217347
**[Test build #49307 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49307/consoleFull)**
for PR 10678 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10734#issuecomment-171219213
**[Test build #49303 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49303/consoleFull)**
for PR 10734 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8532#issuecomment-171223121
Close this PR please @tijoparacka if you're not updating it
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10738#issuecomment-171238791
ping @rxin @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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-171240572
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/10029#issuecomment-171240574
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/10734#issuecomment-171242036
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/10738#issuecomment-171249831
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/10735#discussion_r49560601
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/BenchmarkWholeStageCodegen.scala
---
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-171210808
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/8760#issuecomment-171210609
**[Test build #49294 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49294/consoleFull)**
for PR 8760 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10735#discussion_r49560296
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/BenchmarkWholeStageCodegen.scala
---
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the Apache
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10736#issuecomment-171218362
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10738#issuecomment-171250827
**[Test build #49310 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49310/consoleFull)**
for PR 10738 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10738#issuecomment-171250952
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/10738#issuecomment-171250951
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10735#discussion_r49561357
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/BenchmarkWholeStageCodegen.scala
---
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the Apache
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10735#discussion_r49561388
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/BenchmarkWholeStageCodegen.scala
---
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the Apache
Github user johd01 commented on the pull request:
https://github.com/apache/spark/pull/7943#issuecomment-171216053
Hi
This does not seem to work properly.
After the first nodemanager restart:
2016-01-13 08:22:24,472 ERROR shuffle.ExternalShuffleBlockResolver
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10736#issuecomment-171216790
**[Test build #49301 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49301/consoleFull)**
for PR 10736 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10736#issuecomment-171217004
Test PASSed.
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/10714#issuecomment-171224237
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/10729#issuecomment-171227005
@nraychaudhuri I think this is a step in a good direction, but now if there
is an error, how does the process know to exit? it seems like it just
continues. The
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10738#issuecomment-171239173
ping @marmbrus @liancheng
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10703#issuecomment-171212404
**[Test build #49295 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49295/consoleFull)**
for PR 10703 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10734#discussion_r49561587
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -183,32 +175,38 @@ case class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-171214203
**[Test build #49300 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49300/consoleFull)**
for PR 10029 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10736#issuecomment-171217002
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/10029#discussion_r49562972
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/Covariance.scala
---
@@ -0,0 +1,205 @@
+/*
+ * Licensed to
Github user hemshankar commented on the pull request:
https://github.com/apache/spark/pull/4405#issuecomment-171229397
What do we mean by plumbing of the user name through the UI
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user hemshankar commented on the pull request:
https://github.com/apache/spark/pull/4405#issuecomment-171233550
I have few doubts about running in client mode and cluster mode.
Currently I am using a cloudera hadoop single node cluster (kerberos
enabled.)
In client
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10737#issuecomment-171234319
**[Test build #49304 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49304/consoleFull)**
for PR 10737 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/10738
[HotFox] HotFix for scala style in KinesisBackedBlockRDDSuite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/viirya/spark-1 hotfix-kinesis
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10706#issuecomment-171241181
**[Test build #49306 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49306/consoleFull)**
for PR 10706 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-171214447
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/10029#issuecomment-171214450
Test PASSed.
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/10678#issuecomment-171215649
Based on the comments of @davies , this update is for avoiding the usage of
extra buffer in the recursion function. It should perform faster and make codes
simpler.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10678#issuecomment-171217566
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/10678#issuecomment-171217567
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/10736
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/10678#issuecomment-171218582
@gatorsmile For Subquery/Filter/Join, because they will have the same
output as child/children, we should continue to push the attributes through
them.
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10737#issuecomment-171234700
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/10737#issuecomment-171234698
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/10029#issuecomment-171236853
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/10029#issuecomment-171236848
**[Test build #49309 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49309/consoleFull)**
for PR 10029 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-171239983
**[Test build #49305 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49305/consoleFull)**
for PR 10029 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10738#issuecomment-171240740
**[Test build #49310 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49310/consoleFull)**
for PR 10738 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10731#issuecomment-171249633
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/10731#issuecomment-171249634
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/10731#issuecomment-171249631
**[Test build #49311 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49311/consoleFull)**
for PR 10731 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-171210806
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/10736#issuecomment-171210122
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10737#issuecomment-171211213
**[Test build #49304 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49304/consoleFull)**
for PR 10737 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10737#issuecomment-171209982
Can you update this once https://github.com/apache/spark/pull/10734 is
merged?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10706#issuecomment-171216187
**[Test build #49306 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49306/consoleFull)**
for PR 10706 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10678#issuecomment-171217564
**[Test build #49307 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49307/consoleFull)**
for PR 10678 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10734#issuecomment-171219390
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/10734#issuecomment-171219388
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/10029#issuecomment-171236474
**[Test build #49309 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49309/consoleFull)**
for PR 10029 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10734#issuecomment-171236469
**[Test build #2375 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2375/consoleFull)**
for PR 10734 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10029#issuecomment-171236852
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/10734#issuecomment-171241865
**[Test build #49308 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49308/consoleFull)**
for PR 10734 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10734#issuecomment-171242035
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/10731#issuecomment-171249380
**[Test build #49311 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49311/consoleFull)**
for PR 10731 at commit
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/10729#issuecomment-171255908
@srowen good point, it hangs. But as far as I can see, this is due to a
count-down latch that's not released in case of error:
```
"main" #1 prio=5
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/10724#issuecomment-171258926
test 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10703#issuecomment-171212588
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/10703#issuecomment-171212589
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/10029#issuecomment-171214830
**[Test build #49305 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49305/consoleFull)**
for PR 10029 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10737#issuecomment-171214987
@rxin No problem. I will update 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
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/10735#discussion_r49561979
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/BenchmarkWholeStageCodegen.scala
---
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/10029#discussion_r49562260
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/Covariance.scala
---
@@ -0,0 +1,203 @@
+/*
+ * Licensed to
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/10029#discussion_r49562259
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/Covariance.scala
---
@@ -0,0 +1,203 @@
+/*
+ * Licensed to
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/10029#discussion_r49562404
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/Covariance.scala
---
@@ -0,0 +1,203 @@
+/*
+ * Licensed to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10734#issuecomment-171215882
**[Test build #2375 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2375/consoleFull)**
for PR 10734 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/10029#discussion_r49562322
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/Covariance.scala
---
@@ -0,0 +1,205 @@
+/*
+ * Licensed to
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/10678#discussion_r49563404
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -521,38 +522,90 @@ class Analyzer(
*/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10734#issuecomment-171217947
**[Test build #49308 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49308/consoleFull)**
for PR 10734 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10706#issuecomment-171241464
Test PASSed.
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/10721#issuecomment-171241765
@hhbyyh do you know if it cherry-picks cleanly into other branches?
@jkbradley indicated it didn't. Back-porting to 1.6 makes sense; 1.5 maybe; 1.4
seems pretty old as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10706#issuecomment-171241459
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/10724#issuecomment-171261769
**[Test build #49313 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49313/consoleFull)**
for PR 10724 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10724#issuecomment-171261775
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/10729#issuecomment-171286695
Yes, I see it hanging. I ran this on a Mesos cluster with no roles defined.
```
bin/spark-shell --conf spark.mesos.role=mu --master
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10724#issuecomment-171265799
**[Test build #49314 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49314/consoleFull)**
for PR 10724 at commit
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/10729#discussion_r49588313
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -376,6 +376,7 @@ private[spark] class
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/10724#issuecomment-171262525
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 levin-royl opened a pull request:
https://github.com/apache/spark/pull/10739
Changes to support KMeans with large feature space
The problem:
--
In Spark's KMeans code the center vectors are always represented as dense
vectors. As a result, when
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10724#issuecomment-171261203
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/10724#issuecomment-171261208
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/10724#issuecomment-171261470
**[Test build #49313 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49313/consoleFull)**
for PR 10724 at commit
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/10724#issuecomment-171267786
Something wrong with Jenkins?
---
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/10724#issuecomment-171261771
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/10733#issuecomment-171261693
@cloud-fan "CTE within view" is such a test case.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10724#issuecomment-171266455
**[Test build #49314 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49314/consoleFull)**
for PR 10724 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10724#issuecomment-171266469
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/10724#issuecomment-171266465
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/10739#issuecomment-171272165
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 nraychaudhuri commented on the pull request:
https://github.com/apache/spark/pull/10729#issuecomment-171280201
@dragos do you see it hanging? I introduced markErr method to take care of
the countdown latch. This is called from the error handler.
---
If your project is
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/4405#issuecomment-171383089
@hemshankar Please don't use github to ask questions / point out possible
issues. See http://spark.apache.org/community.html.
---
If your project is set up for it, you
1 - 100 of 746 matches
Mail list logo
