If it means no change to 2.11 support, seems OK to me for Spark 2.4.0. The 2.12 support is separate and has never been mutually compatible with 2.11 builds anyway. (I also hope, suspect that the changes are minimal; tests are already almost entirely passing with no change to the closure cleaner when built for 2.12)
On Wed, Jun 6, 2018 at 1:33 PM Holden Karau <hol...@pigscanfly.ca> wrote: > Just chatted with Dean @ the summit and it sounds like from Adriaan there > is a fix in 2.13 for the API change issue that could be back ported to 2.12 > so how about we try and get this ball rolling? > > It sounds like it would also need a closure cleaner change, which could be > backwards compatible but since it’s such a core component and we might want > to be cautious with it, we could when building for 2.11 use the old cleaner > code and for 2.12 use the new code so we don’t break anyone. > > How do folks feel about this? > >
