The master branch has enough content to justify a release and make
many end-users happy. The naming depends (4.1.0, 4.0.2, 5.0.0) on the
actual content and without doing an exhaustive check I feel that if we
release now we should do a minor bump i.e., 4.1.0. If we start
compiling with JDK17, it is
> I'm not sure there's an upgrade path before Spark 4.0. Any ideas?
We can at least separate the concerns. We can remove the runtime modules
that are the main issue. If we compile against an older version of the Hive
metastore module (leaving it unchanged) that at least has a dramatically
reduced
Hi Hive Community,
I hope everyone is doing well! I wanted to initiate a discussion regarding the
recently introduced _req methods in the Hive Metastore (HMS). There are a few
areas where your insights would be invaluable:
Adoption by Other Projects (Presto/Spark):
Should engines like Presto and