Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2329#issuecomment-55074587
Jenkins, 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
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2318#issuecomment-55075420
Hey All,
Please correct me if I am wrong, my conclusion is that this also will not
help because pom published is not appropriate(Since it does not have dependency
Github user watermen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2216#discussion_r17344850
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/api/java/JavaDStreamLike.scala
---
@@ -50,8 +50,8 @@ trait JavaDStreamLike[T, This :
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/2343
[SPARK-3469] Call all TaskCompletionListeners even if some fail
This is necessary because we rely on this callback interface to clean
resources up. The old behavior would lead to resource leaks.
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-55076950
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2340#issuecomment-55076938
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2323#issuecomment-55076971
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 davies commented on the pull request:
https://github.com/apache/spark/pull/2259#issuecomment-55077329
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2285#issuecomment-55077314
Jenkins, 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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2259#issuecomment-55077384
@JoshRosen The problem that will cause hanging has been fixed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2266#issuecomment-55077558
Thanks! 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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2230#issuecomment-55077709
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2342#issuecomment-55078122
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20080/consoleFull)
for PR 2342 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1823#issuecomment-55078979
Do you mind closing this? This whole code is going to be updated by
https://github.com/apache/spark/pull/2330
---
If your project is set up for it, you can reply to this
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2078#issuecomment-55079128
This no longer merges with master. Do you mind rebasing it? I moved the
files into the o.a.s.network.nio package.
---
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/1846#issuecomment-55080701
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20082/consoleFull)
for PR 1846 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2078#issuecomment-55080894
@rxin I've rebased.
---
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 sarutak closed the pull request at:
https://github.com/apache/spark/pull/1823
---
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 rbraley commented on the pull request:
https://github.com/apache/spark/pull/1685#issuecomment-55081114
This is a critical patch for https://github.com/krasserm/akka-analytics/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2338#issuecomment-55082144
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20081/consoleFull)**
after a configured wait of `120m`.
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-55082152
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20095/consoleFull)
for PR 1031 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2078#issuecomment-55082131
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20094/consoleFull)
for PR 2078 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2230#issuecomment-55082124
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20093/consoleFull)
for PR 2230 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2343#issuecomment-55083964
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 commented on the pull request:
https://github.com/apache/spark/pull/2343#issuecomment-55083955
Jenkins, add to whitelist.
---
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 li-zhihui commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-55084516
Thanks @chenghao-intel It seems the sql unit test failure is fixed.
@andrewor14 Can you retest this again?
---
If your project is set up for it, you can reply
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2216#discussion_r17348838
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/api/java/JavaDStreamLike.scala
---
@@ -50,8 +50,8 @@ trait JavaDStreamLike[T, This :
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-55087507
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20095/consoleFull)
for PR 1031 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2078#issuecomment-55088015
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20094/consoleFull)
for PR 2078 at commit
Github user XuTingjun commented on the pull request:
https://github.com/apache/spark/pull/2073#issuecomment-55088380
Now Spark doesn't support SSL
---
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 allwefantasy commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-55089256
@witgo çäºä½ çæ§è½æµè¯ ä½
éé¢æ²¡ææå°è¿ä»£æ¬¡æ°ãæ¯å¤å°æ¬¡è¿ä»£å¢ï¼ä¸ä¸ªå°æ¶å°±å®æäºã
Github user watermen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2216#discussion_r1735
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/api/java/JavaDStreamLike.scala
---
@@ -50,8 +50,8 @@ trait JavaDStreamLike[T, This :
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2230#issuecomment-55093270
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20093/consoleFull)
for PR 2230 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1106#issuecomment-55093889
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20101/consoleFull)
for PR 1106 at commit
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-55094784
@allwefantasy
æçæµè¯è¯æåºå¤§å°æ¯`196558` 个ææ¡£, `7897767` 个è¯.
è¿ä»£æ¬¡æ°æ¯`100`次.
ä½ ç24ä¸ææ¡£æ»å
±æå¤ä¸ªè¯?
ä½
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-55095034
(Pardon, I think it's important to also summarize in English, as the lingua
franca of the project, for the benefit of other readers.)
---
If your project is set up for
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-55095890
@allwefantasy
æ认为è¿éç代ç ` Document(parts(0).toInt,(0 until
wordInfo.value.size).map(k= values.getOrElse(k,0)).toArray)`
æ¯æç¹é®é¢ç..
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-55096559
@srowen I will try to translate the comments into English
---
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 adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-55098584
The fail is in BroadcastSuite, has nothing to do with this PR...
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2245#issuecomment-55098867
failure is in pyspark...
---
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/1106#issuecomment-55099544
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20101/consoleFull)
for PR 1106 at commit
Github user huozhanfeng commented on the pull request:
https://github.com/apache/spark/pull/2320#issuecomment-55102455
@pwendell @tgravescs Thanks for your advice.
Yes I want to support multiple users all using different credentials and in
our application scenario users
Github user chouqin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2332#discussion_r17355688
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/tree/DecisionTreeSuite.scala ---
@@ -674,6 +676,45 @@ class DecisionTreeSuite extends FunSuite with
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1270#issuecomment-55104337
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20102/consoleFull)
for PR 1270 at commit
GitHub user adrian-wang opened a pull request:
https://github.com/apache/spark/pull/2344
[SPARK-3407][SQL]Add Date type support
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/adrian-wang/spark date
Alternatively you can review
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2344#issuecomment-55110094
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20103/consoleFull)
for PR 2344 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1270#issuecomment-55110210
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20102/consoleFull)
for PR 1270 at commit
GitHub user koeninger opened a pull request:
https://github.com/apache/spark/pull/2345
SPARK-3462 push down filters and projections into Unions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mediacrossinginc/spark SPARK-3462
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2253#issuecomment-55115519
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2345#issuecomment-55117296
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
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/2346
SPARK-3470 [CORE] [STREAMING] Add Closeable / close() to Java context
objects
... that expose a stop() lifecycle method. This doesn't add
`AutoCloseable`, which is Java 7+ only. But it should be
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/792#issuecomment-55122492
@ankurdave yes, i agree with you. like this:
def toEdgePartition(sort: Boolean = true): EdgePartition[ED, VD] = {
}
---
If your project is set up for it,
Github user chouqin commented on the pull request:
https://github.com/apache/spark/pull/2332#issuecomment-55122746
@jkbradley thanks for your replies. as I replied in your comments, I have
changed `minInstancePerNode` to 2 in test cases, and add one more test case to
test that when a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2344#issuecomment-55123057
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20103/consoleFull)
for PR 2344 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2346#issuecomment-55126763
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20104/consoleFull)
for PR 2346 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2332#issuecomment-55126783
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20105/consoleFull)
for PR 2332 at commit
Github user allwefantasy commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-55129263
@witgo é£å°±æ¯æç¯äºé误ï¼å¯¹Document ä¸content
ç解éäºãæ以为content
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/2332#discussion_r17367203
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/tree/DecisionTreeSuite.scala ---
@@ -674,6 +676,45 @@ class DecisionTreeSuite extends FunSuite with
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/2341#issuecomment-55131403
Failure is unrelated to this 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 does
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2346#issuecomment-55132817
The relevant PR: #991
---
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/2332#issuecomment-55135444
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20105/consoleFull)
for PR 2332 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-55136558
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20106/consoleFull)
for PR 1482 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2346#issuecomment-55136925
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20104/consoleFull)
for PR 2346 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/2318#issuecomment-55138035
If there's no way for the maven-install-plugin to fix the existing pom
(instead of generating a minimal pom with no dependencies), then I guess I
don't see any other
GitHub user staple opened a pull request:
https://github.com/apache/spark/pull/2347
[SPARK-1484][MLLIB] Warn when running an iterative algorithm on uncached
data.
Add warnings to KMeans, GeneralizedLinearAlgorithm, and computeSVD when
called with input data that is not cached.
Github user staple commented on the pull request:
https://github.com/apache/spark/pull/2347#issuecomment-55138304
See above where I describe how, for python RDDs, the input data is
automatically cached and then deserialized via a map to an uncached RDD,
requiring deserialization of
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1946#issuecomment-55144780
I'm not for or against the fix, but just wanted to point out that event the
order the OS returns the interfaces is not really reliable. On my machine,
where I constantly
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2347#issuecomment-55145287
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-55145787
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20106/consoleFull)
for PR 1482 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2276#issuecomment-55145976
+1, looks good. Thanks @benoyantony
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/2276
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-55147473
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 this
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/2346#issuecomment-55149328
since spark targets java 7 8, why not just use the correct AutoCloseable?
---
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/2346#issuecomment-55150236
It doesn't target Java 7:
https://github.com/apache/spark/blob/master/pom.xml#L113
---
If your project is set up for it, you can reply to this email and have your
reply
Github user benoyantony commented on the pull request:
https://github.com/apache/spark/pull/2276#issuecomment-55151029
Thank you.
Could one of you please add me as Contributor so that I can assign this
jira to me ?
---
If your project is set up for it, you can reply to this
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2276#issuecomment-55152158
@pwendell can you add @benoyantony as contributor in jira.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2292#issuecomment-55152172
Weird, I've never seen Hive fail to initialize like this before.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2292#issuecomment-55152188
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 mattf commented on the pull request:
https://github.com/apache/spark/pull/2346#issuecomment-55152257
It doesn't target Java 7:
https://github.com/apache/spark/blob/master/pom.xml#L113
you're right. i hope it becomes java 7+ and we can move to AutoCloseable
---
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2291#issuecomment-55152400
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/2346#issuecomment-55152475
`AutoCloseable` is a superinterface of `Closeable`, so, this is already
true. Implementing `Closeable` is a stronger condition, strangely.
---
If your project is set up
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2245#issuecomment-55152467
@JoshRosen, here's an example of the pyspark failure.
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2245#issuecomment-55152478
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-55152587
@JoshRosen, another flakey one in Core
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2245#issuecomment-55153460
Actually, I'm just going to merge... 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2245
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-55154043
Thanks! 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
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/2320#issuecomment-55154141
So it has nothing to do with whom start the spark daemons but with whom
start the driver.
Well, standalone supports cluster mode. In cluster mode, the Worker
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2246
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/2339#discussion_r17377106
--- Diff: ec2/spark_ec2.py ---
@@ -618,6 +620,57 @@ def wait_for_cluster(conn, wait_secs, master_nodes,
slave_nodes):
time.sleep(wait_secs)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2292#issuecomment-55154527
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20107/consoleFull)
for PR 2292 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-55154549
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20109/consoleFull)
for PR 1290 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2291#issuecomment-55154552
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20108/consoleFull)
for PR 2291 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2291#issuecomment-55154697
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20108/consoleFull)
for PR 2291 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2292#issuecomment-55154659
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20107/consoleFull)
for PR 2292 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-55154710
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20109/consoleFull)
for PR 1290 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2339#discussion_r17377246
--- Diff: ec2/spark_ec2.py ---
@@ -618,6 +620,57 @@ def wait_for_cluster(conn, wait_secs, master_nodes,
slave_nodes):
time.sleep(wait_secs)
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1846#discussion_r17377308
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/SQLQuerySuite.scala
---
@@ -47,4 +47,16 @@ class SQLQuerySuite extends QueryTest {
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2339#discussion_r17377782
--- Diff: ec2/spark_ec2.py ---
@@ -60,9 +60,11 @@ def parse_args():
parser.add_option(
-s, --slaves, type=int, default=1,
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2339#discussion_r17377820
--- Diff: ec2/spark_ec2.py ---
@@ -872,7 +925,14 @@ def real_main():
(master_nodes, slave_nodes) = get_existing_cluster(conn, opts,
1 - 100 of 364 matches
Mail list logo
