Github user tedyu commented on a diff in the pull request:
https://github.com/apache/spark/pull/7853#discussion_r39880833
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -96,7 +96,7 @@ class SparkContext(config: SparkConf) extends Logging
with ExecutorAlloc
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8781#discussion_r39880744
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/StreamingContext.scala ---
@@ -610,7 +614,7 @@ class StreamingContext private[streaming] (
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4980#issuecomment-141515406
Shall we close this PR then?
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7853#discussion_r39880463
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -96,7 +96,7 @@ class SparkContext(config: SparkConf) extends Logging
with Executor
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/4980#issuecomment-141514967
Seems that this issue has already fixed by #6833?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8800#issuecomment-141514701
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8800#issuecomment-141514672
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 h
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/8438#issuecomment-141514207
Hi @mccheah , on the mima tests -- those check for binary compatabilities
across spark versions. If you click through to the link for the test build,
you'll see this in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-141513624
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-141513625
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-141513477
[Test build #42664 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42664/console)
for PR 7971 at commit
[`65617fa`](https://github.
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8568#issuecomment-141512317
I'm closing this one. Probably not necessary to backport this one to
branch-1.5.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user liancheng closed the pull request at:
https://github.com/apache/spark/pull/8568
---
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 e
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8768#issuecomment-141508465
[Test build #42671 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42671/consoleFull)
for PR 8768 at commit
[`5e3361a`](https://gith
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/7853#discussion_r39877195
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -96,7 +96,7 @@ class SparkContext(config: SparkConf) extends Logging
with ExecutorAlloc
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8768#issuecomment-141507375
LGTM. Once jenkins is good, I will merge it to master and branch 1.5.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8768#issuecomment-141507003
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8768#issuecomment-141506942
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 h
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8814#issuecomment-141506513
LGTM. Merged into master. 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
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8820#issuecomment-141506427
LGTM. Merged into master. 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8814
---
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 tedyu commented on a diff in the pull request:
https://github.com/apache/spark/pull/7853#discussion_r39876553
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -96,7 +96,7 @@ class SparkContext(config: SparkConf) extends Logging
with ExecutorAlloc
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8819#issuecomment-141505941
@aseigneurin Please send the patch to master branch instead of a release
branch unless it is a bug fix in particular to that branch. You can close this
PR and open anothe
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141506027
@zsxwing How serious is the leak? Under what condition(s) will we see a
significant amount of memory occupied by leaked stuff?
---
If your project is set up for it, you c
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8750#issuecomment-141504537
@viirya We may try to store the schema to a metadata file for the table.
With this way, we can avoid of introducing hacks for writing out null values.
But, we need to cons
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141497995
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141497994
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141497841
[Test build #42663 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42663/console)
for PR 8357 at commit
[`4bc33e0`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8812#issuecomment-141489701
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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141496066
@rxin, should this also go into 1.5.1.?
---
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/8631#issuecomment-141492966
[Test build #42670 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42670/consoleFull)
for PR 8631 at commit
[`854d0bb`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8821#issuecomment-141492693
[Test build #42668 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42668/consoleFull)
for PR 8821 at commit
[`a4cc671`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8812#issuecomment-141491397
[Test build #42669 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42669/consoleFull)
for PR 8812 at commit
[`0ffbbeb`](https://gith
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/8821
[WIP] [SPARK-9392] [SQL] Dataframe drop should work on unresolved columns
Dataframe drop should work on unresolved columns
You can merge this pull request into a Git repository by running:
$
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8631#issuecomment-141489800
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8631#issuecomment-141489727
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8821#issuecomment-141489729
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8821#issuecomment-141489684
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8812#issuecomment-141489757
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8820#issuecomment-141488431
[Test build #42666 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42666/console)
for PR 8820 at commit
[`73a7a64`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8820#issuecomment-141488875
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8820#issuecomment-141488870
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 project
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8812#issuecomment-141487898
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141485911
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141485912
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141485763
[Test build #42665 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42665/console)
for PR 8818 at commit
[`30aa83a`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8816#issuecomment-141485070
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8816#issuecomment-141485068
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 project
Github user saucam commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-141483053
thanks for the merge :)
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8604
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8816#issuecomment-141481615
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8816#issuecomment-141481589
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 h
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-141481281
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 have th
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/8816#issuecomment-141480532
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 t
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/8750#issuecomment-141478922
@yhuai Thanks for commenting this.
You are correct that there will be high storing cost if we store all null
values. But I am not sure how to just write null valu
Github user viirya closed the pull request at:
https://github.com/apache/spark/pull/8735
---
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/8820#issuecomment-141477636
[Test build #42666 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42666/consoleFull)
for PR 8820 at commit
[`73a7a64`](https://gith
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8807#issuecomment-141476530
Belatedly, LGTM. Could just disable them too but this seems fine as well.
---
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/8735#issuecomment-141476345
I think this and SPARK-10571 are duplicates of SPARK-10531; let's at least
retag this, or close the PR, as that's already resolved.
---
If your project is set up for it,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8820#issuecomment-141475740
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8820#issuecomment-141475707
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 h
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8819#issuecomment-141475692
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 an
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/8820
[SPARK-10699] [ML] Support checkpointInterval can be disabled
Currently use can set ```checkpointInterval``` to specify how often should
the cache be checkpointed. But we also need the function t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141474536
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141474726
[Test build #42665 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42665/consoleFull)
for PR 8818 at commit
[`30aa83a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141474569
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 have
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141473588
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8815#issuecomment-141472470
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8815#issuecomment-141472467
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8815#issuecomment-141472362
[Test build #42661 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42661/console)
for PR 8815 at commit
[`a5bd136`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-141470670
[Test build #42664 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42664/consoleFull)
for PR 7971 at commit
[`65617fa`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141469954
[Test build #42662 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42662/console)
for PR 8818 at commit
[`30aa83a`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141470026
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141470024
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8819#issuecomment-141465145
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 pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-141467928
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-141467993
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 have
Github user JDrit commented on a diff in the pull request:
https://github.com/apache/spark/pull/7971#discussion_r39859953
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -794,6 +797,45 @@ class SparkContext(config: SparkConf) extends Logging
with ExecutorAl
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141463713
[Test build #42663 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42663/consoleFull)
for PR 8357 at commit
[`4bc33e0`](https://gith
GitHub user aseigneurin opened a pull request:
https://github.com/apache/spark/pull/8819
Fixed links to the API
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aseigneurin/spark patch-1
Alternatively you can review and apply the
Github user travishegner commented on the pull request:
https://github.com/apache/spark/pull/8780#issuecomment-141462484
That is exactly what I was afraid of. Would the patch make more sense to
*only* check precision for a zero value? Does it ever make sense to have a
precision of zer
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141462018
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 have
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141462133
@marmbrus since SQLContext is thread-safe, I suppose SQLParser is
thread-safe too. So I reopened it. Could you take a look at this one?
---
If your project is set up fo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141461990
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 h
GitHub user zsxwing reopened a pull request:
https://github.com/apache/spark/pull/8357
[SPARK-10155][SQL]Change SqlParser to object to avoid memory leak
Since `scala.util.parsing.combinator.Parsers` is thread-safe since Scala
2.10 (See [SI-4929](https://issues.scala-lang.org/browse/
Github user KaiXinXiaoLei closed the pull request at:
https://github.com/apache/spark/pull/8815
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141458401
[Test build #42662 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42662/consoleFull)
for PR 8818 at commit
[`30aa83a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141457023
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141457002
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 h
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/8818#issuecomment-141456637
@tdas, what do you think?
---
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 t
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/8818
[SPARK-10692][Streaming]Report the batch error to
StreamingListener.onBatchCompleted
Added an `errorMessage` field and set it when a Streaming job is failed.
I have not yet updated the Stre
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8781#issuecomment-141450070
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8781#issuecomment-141450067
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8781#issuecomment-141449968
[Test build #42658 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42658/console)
for PR 8781 at commit
[`d8600cf`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8813#issuecomment-141440394
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8813#issuecomment-141440396
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8813#issuecomment-141440290
[Test build #42654 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42654/console)
for PR 8813 at commit
[`4deb98b`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8816#issuecomment-141433322
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 pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8817#issuecomment-141433319
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 pr
GitHub user dibbhatt opened a pull request:
https://github.com/apache/spark/pull/8817
[SPARK-10694][STREAMING]Prevent Data Loss in Spark Streaming when used with
OFF_HEAP ExternalBlockStore (Tachyon)
The Motivation :
If Streaming application stores the blocks OFF_HEAP, it m
401 - 500 of 618 matches
Mail list logo
