Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/15023
Thanks for understanding! I do hope you guys upgrade eventually, there's a
lot of good stuff and 2.0.1 should be out in the near future. Please do report
any issues you see :)
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15023
**[Test build #3262 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3262/consoleFull)**
for PR 15023 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15023
**[Test build #3262 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3262/consoleFull)**
for PR 15023 at commit
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/15023
This is perfectly understandable, Just in the same way that we err on the
side of caution by not switching to 2.0 branch for prod just now :-)
---
If your project is set up for it, you can
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/15023
Thanks for spending the time to backport this, but it does seem a little
risky to include changes to the configuration system in a maintenance release.
As such, I'd probably error on the side of
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/15023
I'm aware that features are not generally back-ported. The point is, for us
this is a bug, preventing a deployment in production. We thus back-ported the
fix internally and now propose to
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15023
We don't generally backport features to maintenance releases. Pinging
@marmbrus who I believe is currently doing RM for the 1.6 line.
---
If your project is set up for it, you can reply to this
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15023
Please ignore AppVeyor test here. (Please refer
https://github.com/apache/spark/pull/15022#issuecomment-245884867) it seems it
happens only in other branchs as they don't have `appveyor.yml`
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15023
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 project does not have this
