Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4239#discussion_r23679494
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/JobPage.scala ---
@@ -32,7 +32,12 @@ private[ui] class JobPage(parent: JobsTab) extends
WebUIPage(job)
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3812#issuecomment-71816219
Already proposed at https://issues.apache.org/jira/browse/SPARK-5413.
Perhaps we can close this issue and PRs then if that's the way forward.
---
If your project is set
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4246#issuecomment-71816217
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 jinntrance closed the pull request at:
https://github.com/apache/spark/pull/3697
---
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 OopsOutOfMemory opened a pull request:
https://github.com/apache/spark/pull/4249
[SPARK-5324][SQL] Results of describe can't be queried
Make below code works.
```
sql(DESCRIBE test).registerTempTable(describeTest)
sql(SELECT * FROM describeTest).collect()
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/4014#issuecomment-71835068
@chenghao-intel Thanks for comments. I refactor the codes for these issues.
For reusing Hive existing codes, I check the links you mentioned. However,
the codes
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3732#issuecomment-71795113
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/3382#issuecomment-71796637
@fjiang6 It seems that we don't really have a scalable solution at this
time. Do you mind closing this PR? It would be great if you can maintain this
k-medoids
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4238#issuecomment-71798309
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user kul opened a pull request:
https://github.com/apache/spark/pull/4243
[SPARK-5426][SQL] Add SparkSQL Java API helper methods.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kul/spark master
Alternatively you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4241#issuecomment-71803672
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/4241#issuecomment-71803663
[Test build #26214 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26214/consoleFull)
for PR 4241 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/4211#issuecomment-71810049
Sure, let's do it.
---
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 tzolov commented on a diff in the pull request:
https://github.com/apache/spark/pull/4232#discussion_r23677265
--- Diff: pom.xml ---
@@ -105,6 +104,8 @@
moduleexternal/zeromq/module
moduleexamples/module
modulerepl/module
+!--
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/4245#issuecomment-71811080
How about escaping specific characters like `` or `` in each sink instead
of changing the identifier?
---
If your project is set up for it, you can reply to this email
Github user cleaton commented on the pull request:
https://github.com/apache/spark/pull/3868#issuecomment-71843209
Jenkins, test 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 rxin opened a pull request:
https://github.com/apache/spark/pull/4241
[SPARK-5097][SQL] Address DataFrame code review feedback.
Also removed the literal implicit transformation since it is pretty scary
for API design. Instead, created a new lit method for creating
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3732#issuecomment-71796516
[Test build #26216 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26216/consoleFull)
for PR 3732 at commit
Github user OopsOutOfMemory commented on the pull request:
https://github.com/apache/spark/pull/4207#issuecomment-71799906
@yanbohappy thanks for the discussion and the work efforts : )
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4239#issuecomment-71801048
I agree that 5xx means server error, and is not an appropriate response.
But assuming a value of -1 doesn't seem like a great solution -- how about
returning `400 Bad
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4243#issuecomment-71801054
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/3812#issuecomment-71806726
@sarutak I still don't get the purpose of this change, and as you say it
not only potentially broke metrics, but seems to have. Although maybe you can
fix it forward, is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3732#issuecomment-71796124
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/3732#issuecomment-71796119
[Test build #26215 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26215/consoleFull)
for PR 3732 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3732#issuecomment-71797621
[Test build #26210 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26210/consoleFull)
for PR 3732 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3732#issuecomment-71797625
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/3951#issuecomment-71800548
[Test build #26220 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26220/consoleFull)
for PR 3951 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4216#issuecomment-71802635
[Test build #26217 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26217/consoleFull)
for PR 4216 at commit
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/4224#discussion_r23677054
--- Diff: ec2/spark-ec2 ---
@@ -20,6 +20,6 @@
# Preserve the user's CWD so that relative paths are passed correctly to
#+ the underlying
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4211
---
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/3812#issuecomment-71811250
So, how about escaping the specific characters like `` or `` in each sink
instead of changing the identifier?
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4014#issuecomment-71811339
[Test build #26222 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26222/consoleFull)
for PR 4014 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3732#issuecomment-71795022
[Test build #26215 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26215/consoleFull)
for PR 3732 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4241#issuecomment-71795018
[Test build #26214 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26214/consoleFull)
for PR 4241 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3732#issuecomment-71795107
[Test build #26213 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26213/consoleFull)
for PR 3732 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/3933#issuecomment-71796333
@Lewuathe Do you mind closing this PR? If you want to update the official
document, we can do that in another PR. Thanks for the discussion!
---
If your project is set
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672435
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/ChiSqSelector.scala ---
@@ -0,0 +1,86 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672442
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/ChiSqSelector.scala ---
@@ -0,0 +1,86 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672451
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/feature/ChiSqSelectorSuite.scala ---
@@ -0,0 +1,68 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672438
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/ChiSqSelector.scala ---
@@ -0,0 +1,86 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672450
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/feature/ChiSqSelectorSuite.scala ---
@@ -0,0 +1,68 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672445
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/feature/ChiSqSelectorSuite.scala ---
@@ -0,0 +1,68 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672436
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/ChiSqSelector.scala ---
@@ -0,0 +1,86 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672440
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/ChiSqSelector.scala ---
@@ -0,0 +1,86 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672433
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/ChiSqSelector.scala ---
@@ -0,0 +1,86 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4240#issuecomment-71800465
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/4240#issuecomment-71800459
[Test build #26212 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26212/consoleFull)
for PR 4240 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4232#issuecomment-71801249
@ScrapCodes See https://issues.apache.org/jira/browse/SPARK-5428 - it is to
ensure `assembly` is built last.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4216#issuecomment-71802645
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/3732#issuecomment-71803990
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user wangxiaojing commented on the pull request:
https://github.com/apache/spark/pull/3812#issuecomment-71803946
@srowen @andrewor14 This change can affects for users monitoring driver's
metrics. The property is used for metrics value.
eg: `EXTRA_ELEMENT NAME=DESC
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3732#issuecomment-71803978
[Test build #26216 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26216/consoleFull)
for PR 3732 at commit
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/4232#discussion_r23675195
--- Diff: pom.xml ---
@@ -105,6 +104,8 @@
moduleexternal/zeromq/module
moduleexamples/module
modulerepl/module
+!--
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4244#issuecomment-71808734
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/3812#issuecomment-71810090
Sorry I didn't notice this change affects for specific metrics sinks.
I still think this change is needed. The identifier is used for metrics
name so without this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4216#issuecomment-71796968
[Test build #26217 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26217/consoleFull)
for PR 4216 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/3820#issuecomment-71797016
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 adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/4057#issuecomment-71797084
ping @yhuai
---
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/3715#discussion_r23672024
--- Diff: make-distribution.sh ---
@@ -188,6 +188,7 @@ echo Build flags: $@ $DISTDIR/RELEASE
# Copy jars
cp
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4242#issuecomment-71809543
[Test build #26219 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26219/consoleFull)
for PR 4242 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4242#issuecomment-71809558
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/4245#issuecomment-71810748
This could provide a usability regression for people since the name now
appears differently in the UI. Is there any way we can intercept this somewhere
downstream and
Github user aniketbhatnagar commented on the pull request:
https://github.com/apache/spark/pull/3943#issuecomment-71810814
@tsudukim Would you have time this week to look at this please? I was
hoping for this fix to make it in 1.2.1!
---
If your project is set up for it, you can
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/4207#issuecomment-71795859
@yanbohappy thanks for the discussion.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4216#issuecomment-71797429
@vanzin I understand your concern. Although this patch adds many lines, its
scope is actually limited only to standalone cluster mode, and the default
submit behavior
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4238#issuecomment-71798301
[Test build #26211 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26211/consoleFull)
for PR 4238 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4242#issuecomment-71799528
[Test build #26219 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26219/consoleFull)
for PR 4242 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4216#issuecomment-71805342
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/3658
---
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/3951#issuecomment-71809380
[Test build #26220 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26220/consoleFull)
for PR 3951 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3951#issuecomment-71809389
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/4234#issuecomment-71809831
@ankurdave Ah of course. Hm, the thing is there is a loop of
transformations here, so in theory you'd have to save up all the RDD references
and unpersist at the very end
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4245#issuecomment-71810738
[Test build #26221 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26221/consoleFull)
for PR 4245 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3933
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/3870
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/4114
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1480
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/4205
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/3382
---
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/3812#issuecomment-71810650
OK. Can this be fixed by just escaping the value in the XML output? because
if it's `driver` elsewhere then it seems like it would also break the output
elsewhere.
---
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672452
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/feature/ChiSqSelectorSuite.scala ---
@@ -0,0 +1,68 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4216#issuecomment-71799001
[Test build #26218 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26218/consoleFull)
for PR 4216 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1484#discussion_r23672454
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/feature/ChiSqSelectorSuite.scala ---
@@ -0,0 +1,68 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/4230#discussion_r23672455
--- Diff: core/src/test/scala/org/apache/spark/DriverSuite.scala ---
@@ -28,31 +28,30 @@ import org.apache.spark.util.Utils
class DriverSuite
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/4242
[SPARK-5447][SQL] Replaced reference to SchemaRDD with DataFrame.
and
[SPARK-5448][SQL] Make CacheManager a concrete class and field in SQLContext
You can merge this pull request into a Git
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/4245
[HOTFIX] Rename the identifier of driver from `driver` to `driver`
This change is related to #3812.
The identifier of driver is defined as `driver` but this identifier is
used for metrics
Github user tzolov commented on a diff in the pull request:
https://github.com/apache/spark/pull/4232#discussion_r23677757
--- Diff: pom.xml ---
@@ -105,6 +104,8 @@
moduleexternal/zeromq/module
moduleexamples/module
modulerepl/module
+!--
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/3812#issuecomment-71817474
O.K, let's wait for being merged the PR.
---
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 jinntrance opened a pull request:
https://github.com/apache/spark/pull/4247
[MLLIB] SPARK-4846: throw a RuntimeException and give users hints to
increase the minCount
When the vocabSize*vectorSize is larger than Int.MaxValue/8, we try to
throw a RuntimeException.
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/4248
[SPARK-3872][streaming], Rewrite the test for Actor as receiver in spark
streaming.
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4248#issuecomment-71824604
[Test build #26223 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26223/consoleFull)
for PR 4248 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4249#issuecomment-71825690
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 lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/4168#discussion_r23682980
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -226,50 +249,32 @@ private[spark] class ExecutorAllocationManager(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4140#issuecomment-71830252
[Test build #26224 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26224/consoleFull)
for PR 4140 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4140#issuecomment-71830256
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4239#discussion_r23679510
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/JobPage.scala ---
@@ -32,7 +32,12 @@ private[ui] class JobPage(parent: JobsTab) extends
WebUIPage(job)
Github user sarutak closed the pull request at:
https://github.com/apache/spark/pull/4245
---
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/4245#issuecomment-71817663
I found this issue is resolved by updating `com.codahale.metrics` library
from `3.0.0` to `3.1.0` and it's proposed in #4209. So I'll close this PR.
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4014#issuecomment-71819468
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/4014#issuecomment-71819461
[Test build #26222 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26222/consoleFull)
for PR 4014 at commit
1 - 100 of 713 matches
Mail list logo
