Github user gvramana closed the pull request at:
https://github.com/apache/spark/pull/5457
---
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 en
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-114306259
@gvramana Seems SPARK-6675 has been fixed in 1.4 branch and master. Can you
close this one?
---
If your project is set up for it, you can reply to this email and have yo
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-113334989
@gvramana would you mind closing this PR since it's mostly gone stale? I
believe @marmbrus is suggesting a better fix elsewhere.
---
If your project is set up for it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-96767439
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 pro
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-93042944
I think the real problem here is that the initialization of the config is
lazy, and if we want to fix this the approach should look like: #3895
---
If your project is s
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-92390218
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/30
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-92390185
[Test build #30165 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30165/consoleFull)
for PR 5457 at commit
[`6c2ae87`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-92353166
[Test build #30165 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30165/consoleFull)
for PR 5457 at commit
[`6c2ae87`](https://githu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-91945980
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/30
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-91945973
[Test build #30092 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30092/consoleFull)
for PR 5457 at commit
[`76f0400`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-91937390
[Test build #30092 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30092/consoleFull)
for PR 5457 at commit
[`76f0400`](https://githu
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/5457#issuecomment-91937176
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
ena
12 matches
Mail list logo
