Hi Zhihua,
Thanks for preparing the release.
+1(non-binding)
- Checksum: OK
- GPG verify: OK
- All changes labeled with "hive-4.0.1-must" are included in
3af4517eb8cfd9407ad34ed78a0b48b57dfaa264: OK
- Build and basic queries with Tez 0.10.4 and Hive 4.0.1: OK
I compared the git history with Jir
Hi Zsolt,
It's an interesting suggestion. I often use hooks.
It seems true that some hooks or parts of some hooks can be
asynchronous. However, as Stamatis says, some hooks are not safe to be
asynchronous. For example, DisallowTransformHook[1] is expected to be
completed before a DAG starts and i
Thanks for starting this thread.
Last I checked, Aman Raj was driving the backports for branch-3. The
tracking ticket for this effort was
https://issues.apache.org/jira/browse/HIVE-26751 However, I don't see
recent activity on that ticket so I am not sure if they are actively
working on this anymo
If I recall correctly, we were planning to call for a vote to mark 3.x
EOL after the 4.0.1 release. It seems no one is actively pursuing the
3.x release line. Placing the burden of backporting security fixes,
managing the release, running tests (perf/tpcds/bugs), and validating
the release candidat
