-1. Found an issue in a new 2.4 Java API: https://issues.apache.org/jira/browse/SPARK-25644 We should fix it in 2.4.0 to avoid future breaking changes.
Best Regards, Ryan On Mon, Oct 1, 2018 at 7:22 PM Michael Heuer <heue...@gmail.com> wrote: > FYI I’ve open two new issues against 2.4.0 rc2 > > https://issues.apache.org/jira/browse/SPARK-25587 > https://issues.apache.org/jira/browse/SPARK-25588 > > that are regressions against 2.3.1, and may also be present in 2.3.2. > They could use triage or review. > > michael > > > On Oct 1, 2018, at 9:18 PM, Wenchen Fan <cloud0...@gmail.com> wrote: > > This RC fails because of the correctness bug: SPARK-25538 > > I'll start a new RC once the fix( > https://github.com/apache/spark/pull/22602) is merged. > > Thanks, > Wenchen > > On Tue, Oct 2, 2018 at 1:21 AM Sean Owen <sro...@apache.org> wrote: > >> Given that this release is probably still 2 weeks from landing, I don't >> think that waiting on a spark-tensorflow-connector release with TF 1.12 in >> mid-October is a big deal. Users can use the library with Spark 2.3.x for a >> week or two before upgrading, if that's the case. I think this kind of bug >> fix is appropriate for a minor release, while I could see trying to work >> around to keep the buggy behavior in a maintenance release. >> On Mon, Oct 1, 2018 at 12:11 PM Xiangrui Meng <m...@databricks.com> >> wrote: >> >>> >>> IMHO, the use case (spark-tensorflow-connector) is very important. But >>> whether we need to fix it in 2.4 branch depends on the release timeline. >>> See my comment in the JIRA: >>> https://issues.apache.org/jira/browse/SPARK-25378 >>> >>> >
