Thanks Peter and Zoltan for starting this discussion. Apologies for the
delay but I had the impression that I already sent this email.
I definitely agree with the idea of having quarterly releases no matter
what they are called (alpha, beta, or other).
I wouldn't base the decision to move from
Hey,
>> In another email thread
(https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s) Sun Chao mentioned
that other projects (Spark,
>> Iceberg and Trino/Presto) are still depending on old Hive, because the exec-core jar has been removed, and the exec jar contains unshaded
Thanks for reminding me, Peter. There is
https://issues.apache.org/jira/browse/HIVE-25317 but that's for Hive
2.3 and is mostly for the Spark use case. I just created
https://issues.apache.org/jira/browse/HIVE-26220 and marked it as a
blocker.
On Tue, May 10, 2022 at 10:01 PM Peter Vary wrote:
>
In another email thread (
https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s) Sun Chao
mentioned that other projects (Spark,
Iceberg and Trino/Presto) are still depending on old Hive, because the
exec-core jar has been removed, and the exec jar contains unshaded versions
of various
Hi Team,
With Zoltan Haindrich, we have been brainstorming about the next steps after
the 4.0.0-alpha-1 release.
We come up with the following plan:
- Define a desired scope for the 4.0.0 release
- Release minimally quarterly - create alpha release(s) until the scope is
reached
- If the scope
