Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12932
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220519882
I'm going to merge this in master/2.0/1.6. 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220509745
**[Test build #3002 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3002/consoleFull)**
for PR 12932 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220504635
**[Test build #2998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2998/consoleFull)**
for PR 12932 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220503868
**[Test build #3002 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3002/consoleFull)**
for PR 12932 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220503327
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220503326
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/12932#issuecomment-220503213
**[Test build #58930 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58930/consoleFull)**
for PR 12932 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220500453
We should backport this into 1.6 as well.
---
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/12932#issuecomment-220497098
**[Test build #58930 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58930/consoleFull)**
for PR 12932 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220496823
**[Test build #2998 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2998/consoleFull)**
for PR 12932 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220496773
@dosoft Thank you for the PR. What is the memory footprint of a leaked
driver?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220496577
ok to test
---
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/12932#issuecomment-217154231
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
GitHub user dosoft opened a pull request:
https://github.com/apache/spark/pull/12932
[SPARK-14261][SQL] Memory leak in Spark Thrift Server
Fixed memory leak (HiveConf in the CommandProcessorFactory)
You can merge this pull request into a Git repository by running:
$ git
15 matches
Mail list logo
