Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-67596504
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/3617
---
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/3617#issuecomment-67407190
/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
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-67451624
This is a known issue, and the solution provided in this PR LGTM, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-65834619
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-65835734
[Test build #24185 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24185/consoleFull)
for PR 3617 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-65836379
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-65836374
[Test build #24185 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24185/consoleFull)
for PR 3617 at commit
Github user guowei2 commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-65882460
Sorry for that.
i have a mistake about not test with shim12
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-65883022
[Test build #24204 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24204/consoleFull)
for PR 3617 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-65884641
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-65884637
[Test build #24204 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24204/consoleFull)
for PR 3617 at commit
GitHub user guowei2 opened a pull request:
https://github.com/apache/spark/pull/3617
[SPARK-4756][SQL] FIX: sessionToActivePool grow infinitely, even as
sessions expire
**sessionToActivePool** in **SparkSQLOperationManager** grow infinitely,
even as sessions expire.
we should
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3617#issuecomment-65749636
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
14 matches
Mail list logo
