[GitHub] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16279 **[Test build #3534 has finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3534/consoleFull)** for PR 16279 at commit [`27f5796`](https://github.com/apache/spark/commit

[GitHub] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16279 **[Test build #3534 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3534/consoleFull)** for PR 16279 at commit [`27f5796`](https://github.com/apache/spark/commit/

[GitHub] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user AnthonyTruchet commented on the issue: https://github.com/apache/spark/pull/16279 We have backported it to our internal version of Spark anyhow. As told above feel free to close it if you consider this is not worth officially backporting :-) --- If your project is set up

[GitHub] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user sethah commented on the issue: https://github.com/apache/spark/pull/16279 Can we close it? --- 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 i

[GitHub] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user AnthonyTruchet commented on the issue: https://github.com/apache/spark/pull/16279 Ok, thanks for the pointer. I do agree this is a non critical judgement call . --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[GitHub] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user srowen commented on the issue: https://github.com/apache/spark/pull/16279 The guidance such as it is is here: http://spark.apache.org/versioning-policy.html It is in truth mostly a judgment call. Improvements are rarely back-ported to a maintenance branch, but it depen

[GitHub] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user AnthonyTruchet commented on the issue: https://github.com/apache/spark/pull/16279 May I ask why ? There was no conflicts so no additional qualification work is required and this looks like a performance bug fix to me, not a new feature. In order to adjust our contribution

[GitHub] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user AnthonyTruchet commented on the issue: https://github.com/apache/spark/pull/16279 @srowen sorry to bother you but this is just the backport (without any conflict) of #16037. Could you please validate it ? --- If your project is set up for it, you can reply to this

[GitHub] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user srowen commented on the issue: https://github.com/apache/spark/pull/16279 I don't think we would backport this to even 2.1. You can close this. --- 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] spark issue #16279: [SPARK-18471][MLLIB][BACKPORT-2.0] In LBFGS, avoid sendi...

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16279 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 feat