On Hive 2.x, I'm still preparing for another release 2.3.10 (Hive 2.3
branch is being actively maintained so far). Hopefully this will be
the last release in the branch-2 line.
+1 on making Hive 1 EOL for the time being.
Chao
On Wed, Jan 10, 2024 at 8:10 AM Sankar Hariappan
wrote:
>
> +1 for
+1, It is needed only for upgrading from Hive 1.x/2.x to 3.x and not relevant
for 4.x. We can retain it in 3.x release line only.
-Sankar
-Original Message-
From: Attila Turoczy
Sent: Wednesday, January 10, 2024 7:04 PM
To: dev@hive.apache.org
Subject: [EXTERNAL] Re: [DISCUSS]
+1 for making both Hive 1&2 EOL
-Sankar
-Original Message-
From: Attila Turoczy
Sent: Wednesday, January 10, 2024 7:37 PM
To: dev@hive.apache.org
Subject: [EXTERNAL] Re: [DISCUSS] End of life for Hive 1.x, 2.x, 3.x
[You don't often get email from aturo...@cloudera.com.invalid. Learn
+1 for making it EOL for Hive 1 and Hive 2. I do not think these 2 product
branches are relevant in 2023.
-Attila
On Wed, Jan 10, 2024 at 12:59 PM Denys Kuzmenko
wrote:
> +1 for marking Hive 1.x EOL
>
> Assuming no volunteers willing to take ownership of branch-2 maintenance,
> +1 to declare
Big +1 from me. As we shift our focus from ACID to Iceberg I do not think
it is relevant anymore. Also as Butao highlighted it has a CVE as well.
Let's remove it, and if eventually something is needed (highly doubt) then
we can revisit the decision at that time.
Due to the extensive history of
+1 for marking Hive 1.x EOL
Assuming no volunteers willing to take ownership of branch-2 maintenance, +1 to
declare it EOL as well.
Regards,
Denys
+1 for marking Hive 1.x EOL.
I will also take the opportunity to ask again for Hive 2.x. Are there
people willing to take on the maintenance of the branch-2 line? The
people who take on the maintenance of the release line should (as a
bare minimum) ensure that all CVEs (existing and new ones) are
