Re: Pruning many versions embedded into Zeppelin to be able to upgrade to Java 17

2023-12-15 Thread Jongyoul Lee
Hello,

Thank you for your opinion.

I need to explain the previous discussion. In my understanding,
the Zeppelin community has had a conservative policy - which is not an
actual policy but an atmosphere -  to upgrade dependencies including
interpreters. At that time, it seemed reasonable because everything had
been changed a lot so Zeppelin should support multiple versions and should
keep minimum versions to keep the compatibility.

I agree that it has changed recently. Most data platform components provide
the latest version and Zeppelin can follow it. The community, however,
doesn't have much resources to change it. I'm willing to review if someone
tries to change them. In fact, we change the JDK version to 11 recently.

In short, I agree with you and I hope you start to contribute to those
changes one by one.

If you need any help, please let me know.

Best regards,
Jongyoul Lee

2023년 12월 16일 (토) 오후 3:08, Marc Le Bihan 님이 작성:

> Hello,
>
> Reading the message about the 0.11 version being prepared, I downloaded
> the master branch.
>
> Apache Zeppelin should pruned enough to prepare a move allowing it to be
> able to execute in the current active version: Java 17
> Who can execute it, today, with Java 1.8?
> Who has still on its computer Java 1.8, first? And Scala 2.11, and
> Hadoop 2.7, and... ?
>
> What about leaving many of them?
> Leaving all the old versions to 0.10 and lower, and keeping only the
> last one for the next version?
>
> Even the last version of each plugable tool or langage version might be
> currently the most updated already (scala 2.13 is now recommended for
> Spark 3.x, for example, and scala 2.12 is provided). So why bothering
> keeping those preventing Apache Zeppelin to upgrade to Java 17?
>
> What cannot be receive easily (in next months) a version supporting Java
> 17 should be immediately removed, I think. What future does it have?
> It surely blocks other upgrades.
>
> ---
>
> Apache Zeppelin is a nice project that has been helpful for the Java and
> Scala community. It could be again.
> But yet, it is stuck, and it cannot be repaired, I think, if the parts
> that cannot be upgraded aren't removed from it.
>
> Marc Le Bihan



-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net


Pruning many versions embedded into Zeppelin to be able to upgrade to Java 17

2023-12-15 Thread Marc Le Bihan

Hello,

Reading the message about the 0.11 version being prepared, I downloaded 
the master branch.


Apache Zeppelin should pruned enough to prepare a move allowing it to be 
able to execute in the current active version: Java 17

Who can execute it, today, with Java 1.8?
Who has still on its computer Java 1.8, first? And Scala 2.11, and 
Hadoop 2.7, and... ?


What about leaving many of them?
Leaving all the old versions to 0.10 and lower, and keeping only the 
last one for the next version?


Even the last version of each plugable tool or langage version might be 
currently the most updated already (scala 2.13 is now recommended for 
Spark 3.x, for example, and scala 2.12 is provided). So why bothering 
keeping those preventing Apache Zeppelin to upgrade to Java 17?


What cannot be receive easily (in next months) a version supporting Java 
17 should be immediately removed, I think. What future does it have?

It surely blocks other upgrades.

---

Apache Zeppelin is a nice project that has been helpful for the Java and 
Scala community. It could be again.
But yet, it is stuck, and it cannot be repaired, I think, if the parts 
that cannot be upgraded aren't removed from it.


Marc Le Bihan