I opened ZEPPELIN-6134[1] to upgrade the Livy tests from Spark 2.4 with Java 8, Python 3.7 and Scala 2.11, to Spark 3.2 with Python 3.9, Java 11 and Scala 2.12, there is one test failure which is likely caused by Livy-side class loader issue, I disabled it and will try re-enabling once Livy has new releases.
[1] https://github.com/apache/zeppelin/pull/4880 Thanks, Cheng Pan > On Oct 17, 2024, at 14:35, Jongyoul Lee <jongy...@gmail.com> wrote: > > Hello, > > Thank you for checking it. Then, we can modify the test only and include it > to the next release. > > Best regards, > Jongyoul Lee > > > 2024년 10월 17일 (목) 03:21, Jeff Zhang <zjf...@gmail.com>님이 작성: > >> Correct my last comment, I checked the latest code of livy interpreter. It >> only uses livy binary for integration test. For livy interpreter itself, it >> doesn't depend on any livy package. So I suppose livy interpreter still >> work on JDK 11, but the integration test may fail. >> >> >> >> >> On Wed, Oct 16, 2024 at 9:01 AM Jeff Zhang <zjf...@gmail.com> wrote: >> >>> Livy interpreter just uses livy client jar, might still work? >>> >>> On Wed, Oct 16, 2024 at 12:49 AM Philipp Dallig < >> philipp.dal...@gmail.com> >>> wrote: >>> >>>> Hi guys, >>>> >>>> I was trying to drop the JDK 8 CI workflows and realized that livy only >>>> support JDK 8. How should we proceed? I would drop the livy interpreter. >>>> What are your thoughts? >>>> >>>> Best regards >>>> >>>> Philipp >>>> >>> >>> >>> -- >>> Best Regards >>> >>> Jeff Zhang >>> >> >> >> -- >> Best Regards >> >> Jeff Zhang >>
