Kudos to all the people involved! We all know the complexity of doing
major upgrades and this is even more challenging when we are talking
about newer JDKs.
It's really nice to finally start taking advantage of all the recent
improvements that have been made in JDK 17.
Best,
Stamatis
On Sun, Jun
Greate job! Thank all those who participated in this development!
Thanks,
Butao Zhang
On 2025/06/03 08:37:30 László Bodor wrote:
> Team, this is awesome! Thanks for all the hard work—I was following the
> JDK17 PRs, and they were intense. Great job getting it done! 👏🔥
>
> On Tue, 3 Jun 2025 at 1
Team, this is awesome! Thanks for all the hard work—I was following the
JDK17 PRs, and they were intense. Great job getting it done! 👏🔥
On Tue, 3 Jun 2025 at 10:35, Stamatis Zampetakis wrote:
> Kudos to all the people involved! We all know the complexity of doing
> major upgrades and this is eve
Hi,
Fantastic news! This feature has been on our roadmap for quite some time, and
its release marks a huge milestone for the Hive team and community.
A big congratulations to everyone involved.
Regards,
Denys
Thanks, Okumin.
I'll build the distro and check whether it's being packaged. If it's
not, I believe it's permissible — but I'll run it by Legal to be
completely sure.
Also, from a quick scan of other Apache repositories, it seems some
projects are using this as well [1].
That said, I'll explore w
Hi,
Thanks for making it. It's a massive step for us!
I found the compile dependency on "nashorn-core" was newly added,
which is licensed under "gpl-v2-with-the-classpath-exception-license".
I'm not confident that we can distribute the jar file on a release.
I'm still testing the master branch w
Congratulations guys! That's really awesome!
Will test it out and let you know if I run into any bugs!
Thanks everyone !
Simhadri G
On Sat, May 31, 2025, 12:28 AM Ayush Saxena wrote:
> Hi Folks,
>
> The Hive master branch has now been upgraded to JDK 17. This means
> that building or running
Hi Folks,
The Hive master branch has now been upgraded to JDK 17. This means
that building or running the latest code from the master branch will
require JDK 17 going forward.
You're encouraged to try it out and share your feedback. If you
encounter any issues, please feel free to report them here
