Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/6339#issuecomment-125455783
So I'll work on this some more tomorrow and ping when its ready for review
again.
---
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/7709#issuecomment-125456150
[Test build #130 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/130/consoleFull)
for PR 7709 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7709#issuecomment-125455975
Merged build triggered.
---
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/6339#issuecomment-125456124
[Test build #38663 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38663/consoleFull)
for PR 6339 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7709#issuecomment-125455995
Merged build started.
---
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 yjshen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7365#discussion_r35615752
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/Cast.scala
---
@@ -418,51 +418,508 @@ case class Cast(child: Expression,
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/7667#issuecomment-125456560
Thanks, merging 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7667
---
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/6339#issuecomment-125458122
[Test build #38663 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38663/console)
for PR 6339 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7689#issuecomment-125457746
Thanks - going to merge this and submit a pr to fix the remaining issues
tonight.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7682#discussion_r35615980
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/UnsafeRow.java
---
@@ -236,6 +236,41 @@ public Object get(int ordinal) {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6339#issuecomment-125458130
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 MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/7554#discussion_r35615927
--- Diff: python/pyspark/mllib/linalg.py ---
@@ -1152,9 +1156,392 @@ def sparse(numRows, numCols, colPtrs, rowIndices,
values):
return
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/7554#discussion_r35616011
--- Diff: python/pyspark/mllib/linalg.py ---
@@ -1152,9 +1156,392 @@ def sparse(numRows, numCols, colPtrs, rowIndices,
values):
return
GitHub user aarondav opened a pull request:
https://github.com/apache/spark/pull/7717
[SPARK-9397] DataFrame should provide an API to find source data files if
applicable
Certain applications would benefit from being able to inspect DataFrames
that are straightforwardly produced
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/7554#discussion_r35616017
--- Diff: python/pyspark/mllib/linalg.py ---
@@ -1152,9 +1156,392 @@ def sparse(numRows, numCols, colPtrs, rowIndices,
values):
return
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/7554#discussion_r35616054
--- Diff: python/pyspark/mllib/linalg.py ---
@@ -1152,9 +1156,392 @@ def sparse(numRows, numCols, colPtrs, rowIndices,
values):
return
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/7717#issuecomment-125458969
cc @marmbrus @rxin about exposing a new DataFrame API.
---
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/7689
---
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/7716#issuecomment-125459997
[Test build #38653 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38653/console)
for PR 7716 at commit
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/7554#discussion_r35616121
--- Diff: python/pyspark/mllib/linalg.py ---
@@ -1152,9 +1156,392 @@ def sparse(numRows, numCols, colPtrs, rowIndices,
values):
return
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7682#discussion_r35616151
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/UnsafeRow.java
---
@@ -236,6 +236,41 @@ public Object get(int ordinal) {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7717#issuecomment-125460168
Merged build triggered.
---
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/7716#issuecomment-125460061
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/7717#issuecomment-125460181
Merged build started.
---
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/7320#issuecomment-125168047
[Test build #38536 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38536/console)
for PR 7320 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7688#issuecomment-125171415
[Test build #38532 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38532/console)
for PR 7688 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7688#issuecomment-125171461
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/7679#issuecomment-125183242
Merged build started.
---
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/7679#issuecomment-125183213
Merged build triggered.
---
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/7679#issuecomment-125192918
Merged build triggered.
---
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/7679#issuecomment-125192988
Merged build started.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/7463
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7320#issuecomment-125168126
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/7688#issuecomment-125172184
[Test build #113 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/113/console)
for PR 7688 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6986#issuecomment-125173929
[Test build #38533 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38533/console)
for PR 6986 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7238#issuecomment-125173938
[Test build #38530 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38530/console)
for PR 7238 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6986#issuecomment-125174034
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/7238#issuecomment-125174029
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/7679#issuecomment-125177421
[Test build #38538 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38538/consoleFull)
for PR 7679 at commit
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/7554#issuecomment-125182863
Alright, I made some changes to the design.
The main problem was:
RowMatrix initialization needs rows, numRows, numCols for creating a
RowMatrix. However
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7695#issuecomment-125184451
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125190008
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/7679#issuecomment-125195347
Merged build started.
---
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/7679#issuecomment-125195312
Merged build triggered.
---
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/7624#issuecomment-125198012
looks 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 feature
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/7463#issuecomment-125198212
+1. 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 feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125202512
Merged build triggered.
---
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/7679#issuecomment-125202542
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/7696#issuecomment-125206691
Merged build started.
---
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/7696#issuecomment-125206665
Merged build triggered.
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/7693#issuecomment-125209080
cc @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 this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125218441
Merged build started.
---
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/7679#issuecomment-125218386
Merged build triggered.
---
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/7238#issuecomment-125172462
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/6841#issuecomment-125179173
Merged build started.
---
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/6841#issuecomment-125179354
[Test build #38539 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38539/consoleFull)
for PR 6841 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/7561#discussion_r35536002
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -196,6 +220,47 @@ case class RLike(left:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7561#issuecomment-125207689
Merged build started.
---
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/7561#issuecomment-125207657
Merged build triggered.
---
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/7694#issuecomment-125169609
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/7694#issuecomment-125169541
[Test build #38537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38537/console)
for PR 7694 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7674#issuecomment-125174748
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/7693#issuecomment-125180334
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/7455#issuecomment-125180367
[Test build #38534 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38534/console)
for PR 7455 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7455#issuecomment-125180570
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/7693#issuecomment-125180139
[Test build #38535 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38535/console)
for PR 7693 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125195782
[Test build #38543 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38543/consoleFull)
for PR 7679 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7561#issuecomment-125208397
[Test build #38546 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38546/consoleFull)
for PR 7561 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7691#issuecomment-125173712
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/7691#issuecomment-125173572
[Test build #38529 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38529/console)
for PR 7691 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7674#issuecomment-125174641
[Test build #38528 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38528/console)
for PR 7674 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-125179148
Merged build triggered.
---
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/6841#issuecomment-125181526
[Test build #38539 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38539/console)
for PR 6841 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-125181532
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/7696#issuecomment-125207476
[Test build #38545 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38545/consoleFull)
for PR 7696 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125176540
Build started.
---
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/7679#issuecomment-125176488
Build triggered.
---
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/7679#issuecomment-125182118
[Test build #38538 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38538/console)
for PR 7679 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125182146
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 project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7692#issuecomment-125196657
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/7692#issuecomment-125196573
**[Test build #38531 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38531/console)**
for PR 7692 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125198461
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/7431#issuecomment-125199663
the last change was just log level change so this lgtm.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user avulanov opened a pull request:
https://github.com/apache/spark/pull/7695
Pregel example type fix
Pregel example to express single source shortest path from
https://spark.apache.org/docs/latest/graphx-programming-guide.html#pregel-api
does not work due to incorrect
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125184182
[Test build #38540 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38540/consoleFull)
for PR 7679 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125189959
[Test build #38540 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38540/console)
for PR 7679 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125202498
[Test build #38543 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38543/console)
for PR 7679 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125202535
Merged build started.
---
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/7696#issuecomment-125215371
[Test build #38545 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38545/console)
for PR 7696 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7679#issuecomment-125214934
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/7696#issuecomment-125215415
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/7679#issuecomment-125214848
[Test build #38544 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38544/console)
for PR 7679 at commit
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/7532#issuecomment-125178993
@andrewor14 for the question, I mean if at the beginning, the application
requests 5 executors, but later, it simply calls `sc.requestTotalExecutors(3)`
to claim its
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7695#issuecomment-125184255
Merged build triggered.
---
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/7695#issuecomment-125184280
Merged build started.
---
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 chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/7696
[SPARK-9381][SQL][WIP]Migrate JSON data source to the new partitioning data
source
cc @liancheng
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7688#issuecomment-125172236
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/7238#issuecomment-125172432
[Test build #112 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/112/console)
for PR 7238 at commit
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/7532#issuecomment-125180733
if yes, my concern is just on this; this approach requires the user to
explicitly call killExecutors to `truly` release resources for others to
use...that means, the
1 - 100 of 1220 matches
Mail list logo
