Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-55856209
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/123/consoleFull)
for PR 1616 at commit
[`f9330d4`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2330#issuecomment-55856201
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20451/consoleFull)
for PR 2330 at commit
[`a79a259`](https://github.com/a
Github user li-zhihui commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-55856239
@JoshRosen thanks
---
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 fea
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2406#issuecomment-55856872
LGTM; thanks for updating the title! I'm going to merge this now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2406
---
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 enab
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2397#discussion_r17648914
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
@@ -166,3 +166,20 @@ case class DescribeCommand(child: SparkPlan, output
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2397#issuecomment-55857224
LGTM except for the analyzed logical plan issue as mentioned in my last
comment. Thanks for working on this!
---
If your project is set up for it, you can reply to thi
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/2232#issuecomment-55858105
Could this change behavior in cases where the spark.yarn.dist.files is
configured with no scheme? Without this change, it would interpret no scheme
to mean that it's on HD
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2330#issuecomment-55858115
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20452/consoleFull)
for PR 2330 at commit
[`088ed8a`](https://github.com/a
Github user guowei2 commented on the pull request:
https://github.com/apache/spark/pull/2029#issuecomment-55858585
I've run a micro benchmark in my local with 5 records,1500 keys.
Type | OnHeapAggregate | ExternalAggregate (happens 10 spills)
| ---
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2419#issuecomment-55858790
@derrickburns I think these notes can go in code comments? (They each
generate their own email too.)
This is also a big-bang change covering several issues, some o
GitHub user OdinLin opened a pull request:
https://github.com/apache/spark/pull/2423
[SPARK-3550][MLLIB] fix a unresolved reference variable 'nb' bug
variable nb is not reference in the raise log
You can merge this pull request into a Git repository by running:
$ git pull http
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2423#issuecomment-55860478
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 project d
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2378#issuecomment-55860743
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/122/consoleFull)
for PR 2378 at commit
[`e431377`](https://github.com/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2378#issuecomment-55860805
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20453/consoleFull)
for PR 2378 at commit
[`e431377`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-55861628
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/123/consoleFull)
for PR 1616 at commit
[`f9330d4`](https://github.com/
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/2424
[SPARK-3564] Display App ID on HistoryPage
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sarutak/spark display-appid-on-webui
Alternatively y
Github user colorant commented on a diff in the pull request:
https://github.com/apache/spark/pull/2330#discussion_r17650877
--- Diff:
core/src/main/scala/org/apache/spark/network/netty/BlockClientFactory.scala ---
@@ -0,0 +1,182 @@
+/*
+ * Licensed to the Apache Software F
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2330#discussion_r17650983
--- Diff:
core/src/main/scala/org/apache/spark/network/netty/BlockClientFactory.scala ---
@@ -0,0 +1,182 @@
+/*
+ * Licensed to the Apache Software Found
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2424#issuecomment-55862451
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20454/consoleFull)
for PR 2424 at commit
[`417fe90`](https://github.com/ap
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/2410#issuecomment-55862389
One note about this setting is that I'm not sure it works in all settings
-- if you pass it to a driver as a parameter then it's too late to take effect
(the JVM has alrea
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/2425
[SPARK-3543] Write TaskContext in Java and expose it through a static
accessor.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ScrapCodes/s
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17651529
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17651524
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17651575
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2425#issuecomment-55863345
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20455/consoleFull)
for PR 2425 at commit
[`f716fd1`](https://github.com/ap
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17651616
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17651635
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17651668
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17651760
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17651763
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/2426
[SPARK-3566] [BUILD] .gitignore and .rat-excludes should consider cmd file
and Emacs' backup files
You can merge this pull request into a Git repository by running:
$ git pull https://github.
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17651774
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/2427
[SPARK-3565]Fix configuration item not consistent with document
https://issues.apache.org/jira/browse/SPARK-3565
"spark.ports.maxRetries" should be "spark.port.maxRetries". Make the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2226#issuecomment-55863834
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20456/consoleFull)
for PR 2226 at commit
[`5033928`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2427#issuecomment-55864303
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20457/consoleFull)
for PR 2427 at commit
[`3700dba`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2426#issuecomment-55864329
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20458/consoleFull)
for PR 2426 at commit
[`6a0a5eb`](https://github.com/ap
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2403#issuecomment-55864499
I'm not sure what to make of the MIMA errors:
* the type hierarchy of object org.apache.spark.streaming.Duration has
changed in new version. Missing types {scala.r
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2407#issuecomment-55864941
I add a test case to this file, the current master will fail the case
because we missed `Short` in the `primitiveTypes` here. With this new solution,
we can get rid o
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2407#issuecomment-55865221
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20459/consoleFull)
for PR 2407 at commit
[`15762d2`](https://github.com/ap
Github user colorant commented on a diff in the pull request:
https://github.com/apache/spark/pull/2330#discussion_r17652889
--- Diff:
core/src/main/scala/org/apache/spark/network/netty/BlockServer.scala ---
@@ -121,18 +91,18 @@ class BlockServer(conf: NettyConfig, dataProvider:
B
Github user colorant commented on a diff in the pull request:
https://github.com/apache/spark/pull/2330#discussion_r17653172
--- Diff:
core/src/main/scala/org/apache/spark/network/netty/BlockClientFactory.scala ---
@@ -0,0 +1,182 @@
+/*
+ * Licensed to the Apache Software F
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/2425#discussion_r17653450
--- Diff: core/src/main/java/org/apache/spark/TaskContext.java ---
@@ -0,0 +1,176 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under
Github user adrian-wang closed the pull request at:
https://github.com/apache/spark/pull/2355
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2355#issuecomment-55867500
maybe 2407 is better, I'll close 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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2425#issuecomment-55867575
@rxin One side question, Java8ApiSuite(s) don't compile, looks like we have
been overlooking them for a while. May be we could just remove them ?
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2425#issuecomment-55868820
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20461/consoleFull)
for PR 2425 at commit
[`edf945e`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2226#issuecomment-55868821
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20462/consoleFull)
for PR 2226 at commit
[`096bbbc`](https://github.com/ap
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2426#issuecomment-55868873
You can have global gitignore.
https://help.github.com/articles/ignoring-files. I am not sure how many editors
and such we are going to support. Mind closing this PR.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2424#issuecomment-55868956
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20454/consoleFull)
for PR 2424 at commit
[`417fe90`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2427#issuecomment-55869240
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20457/consoleFull)
for PR 2427 at commit
[`3700dba`](https://github.com/a
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2426#issuecomment-55869359
@ScrapCodes Thanks for your comment.
Vim/vi and Emacs is the most popular editors and current .gitignore
considers vim's swp file so Emacs should be considered.
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2426#issuecomment-55869795
There is nothing like spark-env.cmd in the code base ? + Emacs is my editor
of choice too and I add those excludes in gitignore global simply because I can
not go and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2425#issuecomment-55869923
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20455/consoleFull)
for PR 2425 at commit
[`f716fd1`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2344#issuecomment-55870259
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20463/consoleFull)
for PR 2344 at commit
[`413f946`](https://github.com/ap
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2426#issuecomment-55870586
Current code base doesn't include spark-env.sh but user can create and used
by spark-class2.cmd, run-examples2.cmd, compute-classpath.cmd and pyspark2.cmd.
And if
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2226#issuecomment-55872750
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20456/consoleFull)
for PR 2226 at commit
[`5033928`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2425#issuecomment-55873286
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20464/consoleFull)
for PR 2425 at commit
[`a7d5e23`](https://github.com/ap
Github user ScrapCodes closed the pull request at:
https://github.com/apache/spark/pull/1688
---
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/2407#issuecomment-55874010
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20459/consoleFull)
for PR 2407 at commit
[`15762d2`](https://github.com/a
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/2428
[SPARK-3567] appId field in SparkDeploySchedulerBackend should be volatile
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sarutak/spark appid-v
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2425#issuecomment-55875586
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20461/consoleFull)
for PR 2425 at commit
[`edf945e`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2428#issuecomment-55875701
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20465/consoleFull)
for PR 2428 at commit
[`c7d890d`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2426#issuecomment-55876167
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20458/consoleFull)**
after a configured wait of `120m`.
---
If your project i
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2344#issuecomment-55877253
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20463/consoleFull)
for PR 2344 at commit
[`413f946`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2226#issuecomment-55877476
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20462/consoleFull)
for PR 2226 at commit
[`096bbbc`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2425#issuecomment-55879258
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20464/consoleFull)
for PR 2425 at commit
[`a7d5e23`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2428#issuecomment-55881519
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20465/consoleFull)
for PR 2428 at commit
[`c7d890d`](https://github.com/a
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2397#discussion_r17659871
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
@@ -166,3 +166,20 @@ case class DescribeCommand(child: SparkPlan, outpu
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2126#issuecomment-55887296
@jongyoul sorry I don't know what you mean by on Aug?
---
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 adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2344#issuecomment-55889454
Just rebase code, the failure is in spark-core and not in this patch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jongyoul commented on the pull request:
https://github.com/apache/spark/pull/2126#issuecomment-55889694
@tgravescs not seriously, I'm deal with this issue unless it's not fixed
until Sep.
On Wednesday, September 17, 2014, Tom Graves
wrote:
> @jongy
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2126#issuecomment-55892735
Ok, sounds good.
---
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 feat
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2257#issuecomment-55895625
@pwendell @andrewor14 Any concerns with the time on this? I know our
unit tests already take a long time to run but this doesn't seem to bad. I
think going forward
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2198#issuecomment-55895905
@sarutak it is going to be another day or 2 before I can get time to look
at this in detail.
---
If your project is set up for it, you can reply to this email and have
GitHub user mohitjaggi opened a pull request:
https://github.com/apache/spark/pull/2429
add support for zipping a sequence of RDDs
a proposed fix for https://issues.apache.org/jira/browse/SPARK-3489
You can merge this pull request into a Git repository by running:
$ git pull ht
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2429#issuecomment-55896797
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 project d
Github user derrickburns commented on the pull request:
https://github.com/apache/spark/pull/2419#issuecomment-55898846
I agree that some of my comments should go in the code.
As for the Big Bang change, I understand your concern. The distance
functions touches practically ev
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-55900054
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20466/consoleFull)
for PR 1290 at commit
[`f1af6cf`](https://github.com/ap
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2420#issuecomment-55900507
cc @marmbrus @pwendell Dunno if you guys got notified via JIRA of this pull
request or not.
---
If your project is set up for it, you can reply to this email and have y
Github user willb commented on the pull request:
https://github.com/apache/spark/pull/2401#issuecomment-55902476
Here's a somewhat-related concern: it seems like JVM overhead is unlikely
to scale linearly with requested heap size, so maybe a straight-up 15% isn't a
great default? (I
Github user brndnmtthws commented on the pull request:
https://github.com/apache/spark/pull/2401#issuecomment-55903580
That implies that as you grow the heap, you're not adding threads (or other
things that use off-heap memory). I'm not familiar with Spark's execution
model, but I wo
Github user brndnmtthws commented on the pull request:
https://github.com/apache/spark/pull/2401#issuecomment-55903894
Oh, and one more thing you may want to think about is the OS filesystem
buffers. Again, as you scale up the heap, you may want to proportionally
reserve a slice of o
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2198#issuecomment-55904701
@tgravescs Thank you so much!
---
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 hav
Github user nchammas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2014#discussion_r17668529
--- Diff: CONTRIBUTING.md ---
@@ -0,0 +1,12 @@
+## Contributing to Spark
--- End diff --
Having this is pretty nice! I like the banner you ge
GitHub user nchammas opened a pull request:
https://github.com/apache/spark/pull/2430
[Docs] minor grammar fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nchammas/spark patch-2
Alternatively you can review and apply these c
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2430#issuecomment-55906606
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20467/consoleFull)
for PR 2430 at commit
[`d476bfb`](https://github.com/ap
Github user nartz commented on the pull request:
https://github.com/apache/spark/pull/2410#issuecomment-55909584
using `./bin/spark-submit --driver-memory 3g myscript.py` on the command
line works for me
---
If your project is set up for it, you can reply to this email and have your
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2204#issuecomment-55910777
looks good. I tested it on hadoop 0.23 and it works also.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2204
---
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 enab
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-55911175
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20466/consoleFull)
for PR 1290 at commit
[`f1af6cf`](https://github.com/a
Github user darabos commented on the pull request:
https://github.com/apache/spark/pull/1345#issuecomment-55912866
@Forevian, can you please update it to merge cleanly? Then hunt down a
reviewer! It would be great to have this in 1.2. It would make our code
significantly more efficien
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2376#issuecomment-55913971
I tried to reproduce it with the way the test case, but was
unsuccessful.But like the code below does appear the problem, do not know why
```scala
def runGibbsSampli
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2378#issuecomment-55916761
@mengxr it's ready to review now, thanks.
---
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 d
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2379#issuecomment-55916931
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20468/consoleFull)
for PR 2379 at commit
[`dae0120`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2430#issuecomment-55917112
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20467/consoleFull)
for PR 2430 at commit
[`d476bfb`](https://github.com/a
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/2427#issuecomment-55920064
I am not clear why there is an test failed in
org.apache.spark.broadcast.BroadcastSuite, but it seems like it has nothing to
do with this commit.
Could we ret
Github user erikerlandson commented on the pull request:
https://github.com/apache/spark/pull/2401#issuecomment-55920577
Applying soft memory limits via cgroups is one option, for environments
supporting cgroups. Reserve a certain amount of memory, and if it is exceeded
then swapping
Github user brndnmtthws commented on the pull request:
https://github.com/apache/spark/pull/2401#issuecomment-55921158
When you need to provide guarantees for other services, it's better to
stick to hard limits. Having other tasks get randomly OOM killed is a bad
experience.
---
If
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2410#issuecomment-55921974
@ash211 I believe it'll work actually, because we treat `--driver-*`
arguments specially in bash before we launch the driver JVM.
---
If your project is set up for it
1 - 100 of 491 matches
Mail list logo