You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Stamatis Zampetakis <za...@apache.org> on 2024/09/25 09:26:57 UTC
[DISCUSS] Hive 3.x release
Hi all,
Hive 3.1.3 was released on 2022-06-17 and it is the most recent
release of the 3.x line. Two years have passed since then and we still
don't have a new 3.x release. Claiming that we have support for the
3.x line and not getting releases out is hurting the project in
various ways.
I know that there has been some backporting activity on branch-3 but
personally I have no visibility on what is pending and what is the ETA
for the next release.
Is there a realistic plan that could get us a new release in the next
1-2 months?
Best,
Stamatis
[1] https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s
Re: Re: Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Simhadri G <si...@apache.org>.
Hi Everyone,
@Lisoda ,
I have raised a PR in ranger to update the hive version from 3.1 to hive 4
and fix the HIVECONF issues.
PR: https://github.com/apache/ranger/pull/400
Please help with the reviews.
Thanks!
Simhadri G
On Tue, Oct 8, 2024 at 10:31 AM Sankar Hariappan
<Sa...@microsoft.com.invalid> wrote:
> I honour community’s decision to EOL Hive 3.x which is fair based on
> consensus from community.
>
> I would like to acknowledge the efforts put in by contributors like Aman
> to backport 100+ patches from master to branch-3 and reviews from Vihang,
> Peter, Ayush which brought us close to 3.2 release.
>
> Thanks to all who contributed to branch-3 and pls continue to contribute
> to the success of Hive 4.x!
>
>
>
> PS: Pls excuse me if I didn’t callout any other major contributors.
>
>
>
> Thanks,
>
> Sankar
>
> *From:* vihang karajgaonkar <vi...@apache.org>
> *Sent:* 08 October 2024 07:50
> *To:* dev@hive.apache.org
> *Subject:* Re: Re: Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
>
>
>
> Thanks everyone for freely expressing their opinions. Obviously it looks
> like some of the members here have strong opinions on what should be the
> future of Hive 3.x and since the consensus is towards EOLing it, I am not
> going to pursue this anymore.
>
>
>
> Let’s move forward with Hive 4 and make sure we don’t end up in a similar
> situation with Hive 4 in the future.
>
>
>
> Regards,
>
> Vihang
>
>
>
> On Tue, Oct 8, 2024 at 2:17 AM Stamatis Zampetakis <za...@gmail.com>
> wrote:
>
> Declaring Hive 3 as EOL is the right thing to do and as far as I see
> everyone is convinced about this thus I am not planning to change/retract
> my vote in the respective thread.
>
> Based on the current situation the 3.x EOL vote will pass. I was thinking
> that we could postpone the announcement for the 3.x EOL for a short period
> of time (1-2 weeks) but this goes against the will of the community and the
> spirit of the vote.
>
> I understand that this outcome may be a bit disappointing for those people
> that invested quite some effort in a new 3.x release but the truth is that
> it is dragging the project behind.
>
> Let's all do our best to solve any potential adoption blockers for the
> Hive 4 release. To do this though we also need feedback from our users and
> help from the other open source communities. We can't solve problems that
> we don't know they exist and we can't guess what other projects need so
> please create tickets or even better submit PRs to fix those.
>
> Best,
> Stamatis
>
>
>
> On Mon, Oct 7, 2024, 5:35 PM lisoda <li...@yeah.net> wrote:
>
> The main problem is that HIVE4 changed the variable names in HIVECONF,
> which caused some problems.
>
>
>
>
>
>
>
>
>
>
>
>
> At 2024-10-07 23:32:46, "Denys Kuzmenko" <dk...@apache.org> wrote:
>
> >Hi @lisoda
>
> >
>
> >Thanks for bringing up the Ranger issue. It would be very helpful if you could share the JIRA with the issue details. Downstream we are using a version somewhat close to Hive-4.0 and it is fully integrated with Ranger.
>
> >
>
> >Another integration issue that I am familiar is HIVE-28211, that was resolved in a recent HIVE-4.0.1 release
>
> >
>
> >Regards,
>
> >Denys
>
>
RE: Re: Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Sankar Hariappan <Sa...@microsoft.com.INVALID>.
I honour community’s decision to EOL Hive 3.x which is fair based on consensus from community.
I would like to acknowledge the efforts put in by contributors like Aman to backport 100+ patches from master to branch-3 and reviews from Vihang, Peter, Ayush which brought us close to 3.2 release.
Thanks to all who contributed to branch-3 and pls continue to contribute to the success of Hive 4.x!
PS: Pls excuse me if I didn’t callout any other major contributors.
Thanks,
Sankar
From: vihang karajgaonkar <vi...@apache.org>
Sent: 08 October 2024 07:50
To: dev@hive.apache.org
Subject: Re: Re: Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Thanks everyone for freely expressing their opinions. Obviously it looks like some of the members here have strong opinions on what should be the future of Hive 3.x and since the consensus is towards EOLing it, I am not going to pursue this anymore.
Let’s move forward with Hive 4 and make sure we don’t end up in a similar situation with Hive 4 in the future.
Regards,
Vihang
On Tue, Oct 8, 2024 at 2:17 AM Stamatis Zampetakis <za...@gmail.com>> wrote:
Declaring Hive 3 as EOL is the right thing to do and as far as I see everyone is convinced about this thus I am not planning to change/retract my vote in the respective thread.
Based on the current situation the 3.x EOL vote will pass. I was thinking that we could postpone the announcement for the 3.x EOL for a short period of time (1-2 weeks) but this goes against the will of the community and the spirit of the vote.
I understand that this outcome may be a bit disappointing for those people that invested quite some effort in a new 3.x release but the truth is that it is dragging the project behind.
Let's all do our best to solve any potential adoption blockers for the Hive 4 release. To do this though we also need feedback from our users and help from the other open source communities. We can't solve problems that we don't know they exist and we can't guess what other projects need so please create tickets or even better submit PRs to fix those.
Best,
Stamatis
On Mon, Oct 7, 2024, 5:35 PM lisoda <li...@yeah.net>> wrote:
The main problem is that HIVE4 changed the variable names in HIVECONF, which caused some problems.
At 2024-10-07 23:32:46, "Denys Kuzmenko" <dk...@apache.org>> wrote:
>Hi @lisoda
>
>Thanks for bringing up the Ranger issue. It would be very helpful if you could share the JIRA with the issue details. Downstream we are using a version somewhat close to Hive-4.0 and it is fully integrated with Ranger.
>
>Another integration issue that I am familiar is HIVE-28211, that was resolved in a recent HIVE-4.0.1 release
>
>Regards,
>Denys
Re: Re: Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by vihang karajgaonkar <vi...@apache.org>.
Thanks everyone for freely expressing their opinions. Obviously it looks
like some of the members here have strong opinions on what should be the
future of Hive 3.x and since the consensus is towards EOLing it, I am not
going to pursue this anymore.
Let’s move forward with Hive 4 and make sure we don’t end up in a similar
situation with Hive 4 in the future.
Regards,
Vihang
On Tue, Oct 8, 2024 at 2:17 AM Stamatis Zampetakis <za...@gmail.com>
wrote:
> Declaring Hive 3 as EOL is the right thing to do and as far as I see
> everyone is convinced about this thus I am not planning to change/retract
> my vote in the respective thread.
>
> Based on the current situation the 3.x EOL vote will pass. I was thinking
> that we could postpone the announcement for the 3.x EOL for a short period
> of time (1-2 weeks) but this goes against the will of the community and the
> spirit of the vote.
>
> I understand that this outcome may be a bit disappointing for those people
> that invested quite some effort in a new 3.x release but the truth is that
> it is dragging the project behind.
>
> Let's all do our best to solve any potential adoption blockers for the
> Hive 4 release. To do this though we also need feedback from our users and
> help from the other open source communities. We can't solve problems that
> we don't know they exist and we can't guess what other projects need so
> please create tickets or even better submit PRs to fix those.
>
> Best,
> Stamatis
>
> On Mon, Oct 7, 2024, 5:35 PM lisoda <li...@yeah.net> wrote:
>
>> The main problem is that HIVE4 changed the variable names in HIVECONF,
>> which caused some problems.
>>
>>
>>
>>
>>
>>
>> At 2024-10-07 23:32:46, "Denys Kuzmenko" <dk...@apache.org> wrote:
>> >Hi @lisoda
>> >
>> >Thanks for bringing up the Ranger issue. It would be very helpful if you could share the JIRA with the issue details. Downstream we are using a version somewhat close to Hive-4.0 and it is fully integrated with Ranger.
>> >
>> >Another integration issue that I am familiar is HIVE-28211, that was resolved in a recent HIVE-4.0.1 release
>> >
>> >Regards,
>> >Denys
>>
>>
Re: Re: Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Stamatis Zampetakis <za...@gmail.com>.
Declaring Hive 3 as EOL is the right thing to do and as far as I see
everyone is convinced about this thus I am not planning to change/retract
my vote in the respective thread.
Based on the current situation the 3.x EOL vote will pass. I was thinking
that we could postpone the announcement for the 3.x EOL for a short period
of time (1-2 weeks) but this goes against the will of the community and the
spirit of the vote.
I understand that this outcome may be a bit disappointing for those people
that invested quite some effort in a new 3.x release but the truth is that
it is dragging the project behind.
Let's all do our best to solve any potential adoption blockers for the Hive
4 release. To do this though we also need feedback from our users and help
from the other open source communities. We can't solve problems that we
don't know they exist and we can't guess what other projects need so please
create tickets or even better submit PRs to fix those.
Best,
Stamatis
On Mon, Oct 7, 2024, 5:35 PM lisoda <li...@yeah.net> wrote:
> The main problem is that HIVE4 changed the variable names in HIVECONF,
> which caused some problems.
>
>
>
>
>
>
> At 2024-10-07 23:32:46, "Denys Kuzmenko" <dk...@apache.org> wrote:
> >Hi @lisoda
> >
> >Thanks for bringing up the Ranger issue. It would be very helpful if you could share the JIRA with the issue details. Downstream we are using a version somewhat close to Hive-4.0 and it is fully integrated with Ranger.
> >
> >Another integration issue that I am familiar is HIVE-28211, that was resolved in a recent HIVE-4.0.1 release
> >
> >Regards,
> >Denys
>
>
Re:Re: Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by lisoda <li...@yeah.net>.
The main problem is that HIVE4 changed the variable names in HIVECONF, which caused some problems.
At 2024-10-07 23:32:46, "Denys Kuzmenko" <dk...@apache.org> wrote:
>Hi @lisoda
>
>Thanks for bringing up the Ranger issue. It would be very helpful if you could share the JIRA with the issue details. Downstream we are using a version somewhat close to Hive-4.0 and it is fully integrated with Ranger.
>
>Another integration issue that I am familiar is HIVE-28211, that was resolved in a recent HIVE-4.0.1 release
>
>Regards,
>Denys
Re: Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Denys Kuzmenko <dk...@apache.org>.
Hi @lisoda
Thanks for bringing up the Ranger issue. It would be very helpful if you could share the JIRA with the issue details. Downstream we are using a version somewhat close to Hive-4.0 and it is fully integrated with Ranger.
Another integration issue that I am familiar is HIVE-28211, that was resolved in a recent HIVE-4.0.1 release
Regards,
Denys
Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by lisoda <li...@yeah.net>.
Tips:
As of now, one of the primary issues preventing users from upgrading to HIVE4 is the fact that HIVE4 is currently unable to interface with third-party systems such as Apache Ranger because of the many code changes made to HIVE4.It would be great if someone could submit patches to these projects so that they can be supported with HIVE4.
At 2024-10-07 22:06:53, "lisoda" <li...@yeah.net> wrote:
As a long time user of HIVE, I would like to join this discussion.And share some of my opinions.
Due to the bad situation of HIVE3, users are divided into two broad types:
1. Still use HIVE1.X/2.X, and use Spark/Trino+HMS etc. to replace HIVEQL to some extent or completely replace HIVEQL. This part of the user base doesn't care about the dynamics of HIVE, so they don't care if the community EOLs a certain branch.
2. Use solutions provided by third-party vendors for HIVE3.X, such as using HIVE in HDP3.1.5, or using HIVE-MR3. These users are active users of HIVE and are generally more inclined to leave the HIVE3 branch as soon as possible and migrate to the maintained HIVE4. So EOL 3.x will not have much of an impact on this group of users in general. After all, they maintain their own forked version of HIVE3.X.
As of today, the HIVE3 branch still has a lot of correctness issues and other bugs, so I don't see any point in continuing to release versions of the code based on the current branch-3 branch, which won't even work in production anyway. Unless someone can select some patches from the master branch and merge them into branch-3, but I think that's a lot of work.If you want the branch-3 branch to work well, you'll need to continue to port at least a hundred patches from the master branch to the branch-3 branch. In this regard, I think other HIVE downstream vendors like Cloudera/HIVE-MR3 have a lot of say in the matter because they know what's going on. Honestly, in terms of results, the HIVE3 branch is a "disgrace" to the HIVE project, not only does it discourage users from actively using HIVE, but it also causes a large number of HIVE users to be lost.Unless the HIVE community has the energy to fix HIVE3 completely, we'd better stop supporting it and put all our energy into HIVE4 to fix the bad effects of HIVE3 as much as possible.
At 2024-10-05 14:42:15, "Ayush Saxena" <ay...@gmail.com> wrote:
>Some committer only can be a release manager [1] & I don't have
>objections either if folks are ready to release the 3.x line in
>another two weeks with mandatorily cherry-picking & testing whatever
>is there on security@, if possible with some basic testing that in
>order to just release because "I put some backport effort there" --
>"we" don't land up delivering a substandard release.
>
>I will even register my protest with a -1 to this initiative,
>considering it is overall against the wishes of the current set of
>active contributors, & when there were mails shooting the project down
>about the health of the project, that time this spirit wasn't shown,
>nor did I find anyone who was ready to volunteer to take care of
>fixing things on 3.x. If you can't find those emails or ignored
>them...
>
>Statmatis you need to retract your vote on the EOL thread as well, so
>I don't count you in there, I don't think we can play both sides. The
>vote needs to fail, We don't make decisions "individually" but by
>consensus of all...
>
>-Ayush
>
>
>[1] https://infra.apache.org/release-publishing.html#releasemanager
>
>On Sat, 5 Oct 2024 at 11:21, Aman Raj <ra...@microsoft.com.invalid> wrote:
>>
>> Sure I can take up the release manager role for 3.2.0. Thanks Vihang, Sankar and Stamatis for supporting this.
>>
>> Is there an updated doc to follow for making a release since I have never done it before.
>>
>> Thanks,
>> Aman.
>>
>> Get Outlook for Android
>> ________________________________
>> From: vihang karajgaonkar <vi...@apache.org>
>> Sent: Saturday, October 5, 2024 11:07:36 AM
>> To: dev@hive.apache.org <de...@hive.apache.org>
>> Subject: Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
>>
>> Thanks Stamatis!
>>
>> Is this wiki up to date? https://cwiki.apache.org/confluence/display/Hive/HowToRelease#HowToRelease-HiveRelease
>>
>> I will wait for a day or two to see if Aman wants to take the lead here. If not, I can volunteer to release 3.2.0.
>>
>> Thanks,
>> Vihang
>>
>> On Fri, Oct 4, 2024 at 3:28 PM Stamatis Zampetakis <za...@gmail.com> wrote:
>>
>> Hey Vihang,
>>
>> If someone volunteers to become the release manager and can prepare an RC in the next 1-2 weeks then personally I have no problem testing and voting for it.
>>
>> Even though the EOL vote has started we can postpone the announcement if there's an RC in progress.
>>
>> Best,
>> Stamatis
>>
>>
>> On Thu, Oct 3, 2024, 3:58 AM vihang karajgaonkar <vi...@apache.org> wrote:
>>
>> While I agree with the overall sentiment and reasoning that we can all focus on Hive 4.x I would like to register my protest about this decision. There are 411 commits in branch-3 which are not in branch-3.1 most of those are bug fixes on 3.1.3. The work/effort to backport these is already been done and this is not a new effort that we are asking from the community. If all that is needed is to cut a branch, validate it and make a release out of it, I feel that that effort is small enough to be taken up and then officially mark Hive 3.x as EOL.
>>
>> On Tue, Oct 1, 2024 at 9:32 PM Ayush Saxena <ay...@gmail.com> wrote:
>>
>> Marking the 3.x release line EOL has no impact on existing users; they
>> are free to continue using it as they have for the past two years.
>> This decision is primarily about development focus—we’re officially
>> acknowledging that we won’t be dedicating efforts to 3.x anymore,
>> which has already been the case for some time.
>>
>> The processes are designed to support the project's long-term health,
>> and without formally closing this chapter, we risk negatively
>> affecting the project's future. Every good thing comes to an end, and
>> it's better to conclude this phase on a positive note rather than
>> letting it become a burden.
>>
>> Let’s push forward together and focus on Hive 4.x! I will start a vote
>> thread for marking the end of 3.x soon.
>>
>>
>> -Ayush
>>
>> On Mon, 30 Sept 2024 at 13:29, Denys Kuzmenko <dk...@apache.org> wrote:
>> >
>> > Hive 3.1 is certainly the most widely adopted release line, however, we do not see any activity on this line, even in terms of providing security fixes and CVE backports. Hive 3.1.3, the most recent release of the 3.x, was released on 2022-06-17.
>> >
>> > We don't want to scatter our resources so we focus on Hive 4.0 and would like to encourage everyone to start using Hive 4.0 where we resolved numerous critical bug and security fixes, introduced number of improvements and new features.
Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by lisoda <li...@yeah.net>.
As a long time user of HIVE, I would like to join this discussion.And share some of my opinions.
Due to the bad situation of HIVE3, users are divided into two broad types:
1. Still use HIVE1.X/2.X, and use Spark/Trino+HMS etc. to replace HIVEQL to some extent or completely replace HIVEQL. This part of the user base doesn't care about the dynamics of HIVE, so they don't care if the community EOLs a certain branch.
2. Use solutions provided by third-party vendors for HIVE3.X, such as using HIVE in HDP3.1.5, or using HIVE-MR3. These users are active users of HIVE and are generally more inclined to leave the HIVE3 branch as soon as possible and migrate to the maintained HIVE4. So EOL 3.x will not have much of an impact on this group of users in general. After all, they maintain their own forked version of HIVE3.X.
As of today, the HIVE3 branch still has a lot of correctness issues and other bugs, so I don't see any point in continuing to release versions of the code based on the current branch-3 branch, which won't even work in production anyway. Unless someone can select some patches from the master branch and merge them into branch-3, but I think that's a lot of work.If you want the branch-3 branch to work well, you'll need to continue to port at least a hundred patches from the master branch to the branch-3 branch. In this regard, I think other HIVE downstream vendors like Cloudera/HIVE-MR3 have a lot of say in the matter because they know what's going on. Honestly, in terms of results, the HIVE3 branch is a "disgrace" to the HIVE project, not only does it discourage users from actively using HIVE, but it also causes a large number of HIVE users to be lost.Unless the HIVE community has the energy to fix HIVE3 completely, we'd better stop supporting it and put all our energy into HIVE4 to fix the bad effects of HIVE3 as much as possible.
At 2024-10-05 14:42:15, "Ayush Saxena" <ay...@gmail.com> wrote:
>Some committer only can be a release manager [1] & I don't have
>objections either if folks are ready to release the 3.x line in
>another two weeks with mandatorily cherry-picking & testing whatever
>is there on security@, if possible with some basic testing that in
>order to just release because "I put some backport effort there" --
>"we" don't land up delivering a substandard release.
>
>I will even register my protest with a -1 to this initiative,
>considering it is overall against the wishes of the current set of
>active contributors, & when there were mails shooting the project down
>about the health of the project, that time this spirit wasn't shown,
>nor did I find anyone who was ready to volunteer to take care of
>fixing things on 3.x. If you can't find those emails or ignored
>them...
>
>Statmatis you need to retract your vote on the EOL thread as well, so
>I don't count you in there, I don't think we can play both sides. The
>vote needs to fail, We don't make decisions "individually" but by
>consensus of all...
>
>-Ayush
>
>
>[1] https://infra.apache.org/release-publishing.html#releasemanager
>
>On Sat, 5 Oct 2024 at 11:21, Aman Raj <ra...@microsoft.com.invalid> wrote:
>>
>> Sure I can take up the release manager role for 3.2.0. Thanks Vihang, Sankar and Stamatis for supporting this.
>>
>> Is there an updated doc to follow for making a release since I have never done it before.
>>
>> Thanks,
>> Aman.
>>
>> Get Outlook for Android
>> ________________________________
>> From: vihang karajgaonkar <vi...@apache.org>
>> Sent: Saturday, October 5, 2024 11:07:36 AM
>> To: dev@hive.apache.org <de...@hive.apache.org>
>> Subject: Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
>>
>> Thanks Stamatis!
>>
>> Is this wiki up to date? https://cwiki.apache.org/confluence/display/Hive/HowToRelease#HowToRelease-HiveRelease
>>
>> I will wait for a day or two to see if Aman wants to take the lead here. If not, I can volunteer to release 3.2.0.
>>
>> Thanks,
>> Vihang
>>
>> On Fri, Oct 4, 2024 at 3:28 PM Stamatis Zampetakis <za...@gmail.com> wrote:
>>
>> Hey Vihang,
>>
>> If someone volunteers to become the release manager and can prepare an RC in the next 1-2 weeks then personally I have no problem testing and voting for it.
>>
>> Even though the EOL vote has started we can postpone the announcement if there's an RC in progress.
>>
>> Best,
>> Stamatis
>>
>>
>> On Thu, Oct 3, 2024, 3:58 AM vihang karajgaonkar <vi...@apache.org> wrote:
>>
>> While I agree with the overall sentiment and reasoning that we can all focus on Hive 4.x I would like to register my protest about this decision. There are 411 commits in branch-3 which are not in branch-3.1 most of those are bug fixes on 3.1.3. The work/effort to backport these is already been done and this is not a new effort that we are asking from the community. If all that is needed is to cut a branch, validate it and make a release out of it, I feel that that effort is small enough to be taken up and then officially mark Hive 3.x as EOL.
>>
>> On Tue, Oct 1, 2024 at 9:32 PM Ayush Saxena <ay...@gmail.com> wrote:
>>
>> Marking the 3.x release line EOL has no impact on existing users; they
>> are free to continue using it as they have for the past two years.
>> This decision is primarily about development focus—we’re officially
>> acknowledging that we won’t be dedicating efforts to 3.x anymore,
>> which has already been the case for some time.
>>
>> The processes are designed to support the project's long-term health,
>> and without formally closing this chapter, we risk negatively
>> affecting the project's future. Every good thing comes to an end, and
>> it's better to conclude this phase on a positive note rather than
>> letting it become a burden.
>>
>> Let’s push forward together and focus on Hive 4.x! I will start a vote
>> thread for marking the end of 3.x soon.
>>
>>
>> -Ayush
>>
>> On Mon, 30 Sept 2024 at 13:29, Denys Kuzmenko <dk...@apache.org> wrote:
>> >
>> > Hive 3.1 is certainly the most widely adopted release line, however, we do not see any activity on this line, even in terms of providing security fixes and CVE backports. Hive 3.1.3, the most recent release of the 3.x, was released on 2022-06-17.
>> >
>> > We don't want to scatter our resources so we focus on Hive 4.0 and would like to encourage everyone to start using Hive 4.0 where we resolved numerous critical bug and security fixes, introduced number of improvements and new features.
Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Ayush Saxena <ay...@gmail.com>.
Some committer only can be a release manager [1] & I don't have
objections either if folks are ready to release the 3.x line in
another two weeks with mandatorily cherry-picking & testing whatever
is there on security@, if possible with some basic testing that in
order to just release because "I put some backport effort there" --
"we" don't land up delivering a substandard release.
I will even register my protest with a -1 to this initiative,
considering it is overall against the wishes of the current set of
active contributors, & when there were mails shooting the project down
about the health of the project, that time this spirit wasn't shown,
nor did I find anyone who was ready to volunteer to take care of
fixing things on 3.x. If you can't find those emails or ignored
them...
Statmatis you need to retract your vote on the EOL thread as well, so
I don't count you in there, I don't think we can play both sides. The
vote needs to fail, We don't make decisions "individually" but by
consensus of all...
-Ayush
[1] https://infra.apache.org/release-publishing.html#releasemanager
On Sat, 5 Oct 2024 at 11:21, Aman Raj <ra...@microsoft.com.invalid> wrote:
>
> Sure I can take up the release manager role for 3.2.0. Thanks Vihang, Sankar and Stamatis for supporting this.
>
> Is there an updated doc to follow for making a release since I have never done it before.
>
> Thanks,
> Aman.
>
> Get Outlook for Android
> ________________________________
> From: vihang karajgaonkar <vi...@apache.org>
> Sent: Saturday, October 5, 2024 11:07:36 AM
> To: dev@hive.apache.org <de...@hive.apache.org>
> Subject: Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
>
> Thanks Stamatis!
>
> Is this wiki up to date? https://cwiki.apache.org/confluence/display/Hive/HowToRelease#HowToRelease-HiveRelease
>
> I will wait for a day or two to see if Aman wants to take the lead here. If not, I can volunteer to release 3.2.0.
>
> Thanks,
> Vihang
>
> On Fri, Oct 4, 2024 at 3:28 PM Stamatis Zampetakis <za...@gmail.com> wrote:
>
> Hey Vihang,
>
> If someone volunteers to become the release manager and can prepare an RC in the next 1-2 weeks then personally I have no problem testing and voting for it.
>
> Even though the EOL vote has started we can postpone the announcement if there's an RC in progress.
>
> Best,
> Stamatis
>
>
> On Thu, Oct 3, 2024, 3:58 AM vihang karajgaonkar <vi...@apache.org> wrote:
>
> While I agree with the overall sentiment and reasoning that we can all focus on Hive 4.x I would like to register my protest about this decision. There are 411 commits in branch-3 which are not in branch-3.1 most of those are bug fixes on 3.1.3. The work/effort to backport these is already been done and this is not a new effort that we are asking from the community. If all that is needed is to cut a branch, validate it and make a release out of it, I feel that that effort is small enough to be taken up and then officially mark Hive 3.x as EOL.
>
> On Tue, Oct 1, 2024 at 9:32 PM Ayush Saxena <ay...@gmail.com> wrote:
>
> Marking the 3.x release line EOL has no impact on existing users; they
> are free to continue using it as they have for the past two years.
> This decision is primarily about development focus—we’re officially
> acknowledging that we won’t be dedicating efforts to 3.x anymore,
> which has already been the case for some time.
>
> The processes are designed to support the project's long-term health,
> and without formally closing this chapter, we risk negatively
> affecting the project's future. Every good thing comes to an end, and
> it's better to conclude this phase on a positive note rather than
> letting it become a burden.
>
> Let’s push forward together and focus on Hive 4.x! I will start a vote
> thread for marking the end of 3.x soon.
>
>
> -Ayush
>
> On Mon, 30 Sept 2024 at 13:29, Denys Kuzmenko <dk...@apache.org> wrote:
> >
> > Hive 3.1 is certainly the most widely adopted release line, however, we do not see any activity on this line, even in terms of providing security fixes and CVE backports. Hive 3.1.3, the most recent release of the 3.x, was released on 2022-06-17.
> >
> > We don't want to scatter our resources so we focus on Hive 4.0 and would like to encourage everyone to start using Hive 4.0 where we resolved numerous critical bug and security fixes, introduced number of improvements and new features.
Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Aman Raj <ra...@microsoft.com.INVALID>.
Sure I can take up the release manager role for 3.2.0. Thanks Vihang, Sankar and Stamatis for supporting this.
Is there an updated doc to follow for making a release since I have never done it before.
Thanks,
Aman.
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: vihang karajgaonkar <vi...@apache.org>
Sent: Saturday, October 5, 2024 11:07:36 AM
To: dev@hive.apache.org <de...@hive.apache.org>
Subject: Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Thanks Stamatis!
Is this wiki up to date? https://cwiki.apache.org/confluence/display/Hive/HowToRelease#HowToRelease-HiveRelease
I will wait for a day or two to see if Aman wants to take the lead here. If not, I can volunteer to release 3.2.0.
Thanks,
Vihang
On Fri, Oct 4, 2024 at 3:28 PM Stamatis Zampetakis <za...@gmail.com>> wrote:
Hey Vihang,
If someone volunteers to become the release manager and can prepare an RC in the next 1-2 weeks then personally I have no problem testing and voting for it.
Even though the EOL vote has started we can postpone the announcement if there's an RC in progress.
Best,
Stamatis
On Thu, Oct 3, 2024, 3:58 AM vihang karajgaonkar <vi...@apache.org>> wrote:
While I agree with the overall sentiment and reasoning that we can all focus on Hive 4.x I would like to register my protest about this decision. There are 411 commits in branch-3 which are not in branch-3.1 most of those are bug fixes on 3.1.3. The work/effort to backport these is already been done and this is not a new effort that we are asking from the community. If all that is needed is to cut a branch, validate it and make a release out of it, I feel that that effort is small enough to be taken up and then officially mark Hive 3.x as EOL.
On Tue, Oct 1, 2024 at 9:32 PM Ayush Saxena <ay...@gmail.com>> wrote:
Marking the 3.x release line EOL has no impact on existing users; they
are free to continue using it as they have for the past two years.
This decision is primarily about development focus—we’re officially
acknowledging that we won’t be dedicating efforts to 3.x anymore,
which has already been the case for some time.
The processes are designed to support the project's long-term health,
and without formally closing this chapter, we risk negatively
affecting the project's future. Every good thing comes to an end, and
it's better to conclude this phase on a positive note rather than
letting it become a burden.
Let’s push forward together and focus on Hive 4.x! I will start a vote
thread for marking the end of 3.x soon.
-Ayush
On Mon, 30 Sept 2024 at 13:29, Denys Kuzmenko <dk...@apache.org>> wrote:
>
> Hive 3.1 is certainly the most widely adopted release line, however, we do not see any activity on this line, even in terms of providing security fixes and CVE backports. Hive 3.1.3, the most recent release of the 3.x, was released on 2022-06-17.
>
> We don't want to scatter our resources so we focus on Hive 4.0 and would like to encourage everyone to start using Hive 4.0 where we resolved numerous critical bug and security fixes, introduced number of improvements and new features.
Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by vihang karajgaonkar <vi...@apache.org>.
Thanks Stamatis!
Is this wiki up to date?
https://cwiki.apache.org/confluence/display/Hive/HowToRelease#HowToRelease-HiveRelease
I will wait for a day or two to see if Aman wants to take the lead here. If
not, I can volunteer to release 3.2.0.
Thanks,
Vihang
On Fri, Oct 4, 2024 at 3:28 PM Stamatis Zampetakis <za...@gmail.com>
wrote:
> Hey Vihang,
>
> If someone volunteers to become the release manager and can prepare an RC
> in the next 1-2 weeks then personally I have no problem testing and voting
> for it.
>
> Even though the EOL vote has started we can postpone the announcement if
> there's an RC in progress.
>
> Best,
> Stamatis
>
> On Thu, Oct 3, 2024, 3:58 AM vihang karajgaonkar <vi...@apache.org>
> wrote:
>
>> While I agree with the overall sentiment and reasoning that we can all
>> focus on Hive 4.x I would like to register my protest about this decision.
>> There are 411 commits in branch-3 which are not in branch-3.1 most of those
>> are bug fixes on 3.1.3. The work/effort to backport these is already been
>> done and this is not a new effort that we are asking from the community. If
>> all that is needed is to cut a branch, validate it and make a release out
>> of it, I feel that that effort is small enough to be taken up and then
>> officially mark Hive 3.x as EOL.
>>
>> On Tue, Oct 1, 2024 at 9:32 PM Ayush Saxena <ay...@gmail.com> wrote:
>>
>>> Marking the 3.x release line EOL has no impact on existing users; they
>>> are free to continue using it as they have for the past two years.
>>> This decision is primarily about development focus—we’re officially
>>> acknowledging that we won’t be dedicating efforts to 3.x anymore,
>>> which has already been the case for some time.
>>>
>>> The processes are designed to support the project's long-term health,
>>> and without formally closing this chapter, we risk negatively
>>> affecting the project's future. Every good thing comes to an end, and
>>> it's better to conclude this phase on a positive note rather than
>>> letting it become a burden.
>>>
>>> Let’s push forward together and focus on Hive 4.x! I will start a vote
>>> thread for marking the end of 3.x soon.
>>>
>>>
>>> -Ayush
>>>
>>> On Mon, 30 Sept 2024 at 13:29, Denys Kuzmenko <dk...@apache.org>
>>> wrote:
>>> >
>>> > Hive 3.1 is certainly the most widely adopted release line, however,
>>> we do not see any activity on this line, even in terms of providing
>>> security fixes and CVE backports. Hive 3.1.3, the most recent release of
>>> the 3.x, was released on 2022-06-17.
>>> >
>>> > We don't want to scatter our resources so we focus on Hive 4.0 and
>>> would like to encourage everyone to start using Hive 4.0 where we resolved
>>> numerous critical bug and security fixes, introduced number of improvements
>>> and new features.
>>>
>>
Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Stamatis Zampetakis <za...@gmail.com>.
Hey Vihang,
If someone volunteers to become the release manager and can prepare an RC
in the next 1-2 weeks then personally I have no problem testing and voting
for it.
Even though the EOL vote has started we can postpone the announcement if
there's an RC in progress.
Best,
Stamatis
On Thu, Oct 3, 2024, 3:58 AM vihang karajgaonkar <vi...@apache.org>
wrote:
> While I agree with the overall sentiment and reasoning that we can all
> focus on Hive 4.x I would like to register my protest about this decision.
> There are 411 commits in branch-3 which are not in branch-3.1 most of those
> are bug fixes on 3.1.3. The work/effort to backport these is already been
> done and this is not a new effort that we are asking from the community. If
> all that is needed is to cut a branch, validate it and make a release out
> of it, I feel that that effort is small enough to be taken up and then
> officially mark Hive 3.x as EOL.
>
> On Tue, Oct 1, 2024 at 9:32 PM Ayush Saxena <ay...@gmail.com> wrote:
>
>> Marking the 3.x release line EOL has no impact on existing users; they
>> are free to continue using it as they have for the past two years.
>> This decision is primarily about development focus—we’re officially
>> acknowledging that we won’t be dedicating efforts to 3.x anymore,
>> which has already been the case for some time.
>>
>> The processes are designed to support the project's long-term health,
>> and without formally closing this chapter, we risk negatively
>> affecting the project's future. Every good thing comes to an end, and
>> it's better to conclude this phase on a positive note rather than
>> letting it become a burden.
>>
>> Let’s push forward together and focus on Hive 4.x! I will start a vote
>> thread for marking the end of 3.x soon.
>>
>>
>> -Ayush
>>
>> On Mon, 30 Sept 2024 at 13:29, Denys Kuzmenko <dk...@apache.org>
>> wrote:
>> >
>> > Hive 3.1 is certainly the most widely adopted release line, however, we
>> do not see any activity on this line, even in terms of providing security
>> fixes and CVE backports. Hive 3.1.3, the most recent release of the 3.x,
>> was released on 2022-06-17.
>> >
>> > We don't want to scatter our resources so we focus on Hive 4.0 and
>> would like to encourage everyone to start using Hive 4.0 where we resolved
>> numerous critical bug and security fixes, introduced number of improvements
>> and new features.
>>
>
Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by vihang karajgaonkar <vi...@apache.org>.
While I agree with the overall sentiment and reasoning that we can all
focus on Hive 4.x I would like to register my protest about this decision.
There are 411 commits in branch-3 which are not in branch-3.1 most of those
are bug fixes on 3.1.3. The work/effort to backport these is already been
done and this is not a new effort that we are asking from the community. If
all that is needed is to cut a branch, validate it and make a release out
of it, I feel that that effort is small enough to be taken up and then
officially mark Hive 3.x as EOL.
On Tue, Oct 1, 2024 at 9:32 PM Ayush Saxena <ay...@gmail.com> wrote:
> Marking the 3.x release line EOL has no impact on existing users; they
> are free to continue using it as they have for the past two years.
> This decision is primarily about development focus—we’re officially
> acknowledging that we won’t be dedicating efforts to 3.x anymore,
> which has already been the case for some time.
>
> The processes are designed to support the project's long-term health,
> and without formally closing this chapter, we risk negatively
> affecting the project's future. Every good thing comes to an end, and
> it's better to conclude this phase on a positive note rather than
> letting it become a burden.
>
> Let’s push forward together and focus on Hive 4.x! I will start a vote
> thread for marking the end of 3.x soon.
>
>
> -Ayush
>
> On Mon, 30 Sept 2024 at 13:29, Denys Kuzmenko <dk...@apache.org>
> wrote:
> >
> > Hive 3.1 is certainly the most widely adopted release line, however, we
> do not see any activity on this line, even in terms of providing security
> fixes and CVE backports. Hive 3.1.3, the most recent release of the 3.x,
> was released on 2022-06-17.
> >
> > We don't want to scatter our resources so we focus on Hive 4.0 and would
> like to encourage everyone to start using Hive 4.0 where we resolved
> numerous critical bug and security fixes, introduced number of improvements
> and new features.
>
Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Ayush Saxena <ay...@gmail.com>.
Marking the 3.x release line EOL has no impact on existing users; they
are free to continue using it as they have for the past two years.
This decision is primarily about development focus—we’re officially
acknowledging that we won’t be dedicating efforts to 3.x anymore,
which has already been the case for some time.
The processes are designed to support the project's long-term health,
and without formally closing this chapter, we risk negatively
affecting the project's future. Every good thing comes to an end, and
it's better to conclude this phase on a positive note rather than
letting it become a burden.
Let’s push forward together and focus on Hive 4.x! I will start a vote
thread for marking the end of 3.x soon.
-Ayush
On Mon, 30 Sept 2024 at 13:29, Denys Kuzmenko <dk...@apache.org> wrote:
>
> Hive 3.1 is certainly the most widely adopted release line, however, we do not see any activity on this line, even in terms of providing security fixes and CVE backports. Hive 3.1.3, the most recent release of the 3.x, was released on 2022-06-17.
>
> We don't want to scatter our resources so we focus on Hive 4.0 and would like to encourage everyone to start using Hive 4.0 where we resolved numerous critical bug and security fixes, introduced number of improvements and new features.
RE: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Denys Kuzmenko <dk...@apache.org>.
Hive 3.1 is certainly the most widely adopted release line, however, we do not see any activity on this line, even in terms of providing security fixes and CVE backports. Hive 3.1.3, the most recent release of the 3.x, was released on 2022-06-17.
We don't want to scatter our resources so we focus on Hive 4.0 and would like to encourage everyone to start using Hive 4.0 where we resolved numerous critical bug and security fixes, introduced number of improvements and new features.
RE: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Posted by Sankar Hariappan <Sa...@microsoft.com.INVALID>.
Thanks for bringing up this discussion!
I think, Hive 3.1 is widely adopted and most of the users are interested on security fixes only. So, having another release (3.2) out of branch-3 head including all CVE fixes would be helpful. Also, since Hive 4 is recently released and need sometime to stabilize, if 3.x goes EOL, it may push the users out of Hive.
Thanks,
Sankar
From: Simhadri G <si...@gmail.com>
Sent: 28 September 2024 23:26
To: dev@hive.apache.org
Subject: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
I agree with Ayush and Butao Zhang.
Hive 4 introduces numerous new features, critical bug and security fixes, and significant performance improvements. Given that hive 4 has over 5000 commits compared to Hive 3, backporting changes from hive 4 to hive 3 would be a tedious task due to high possibility of merge conflicts. I believe it would be more productive to focus our active development efforts on the latest master, rather than continuing to maintain and release Hive 3.
I am +1 for marking 3.x EOL.
Thanks!
Simhadri G
On Sat, Sep 28, 2024 at 1:29 PM Butao Zhang <bu...@163.com>> wrote:
Agreed with Ayush. I think we won't put much effort into 3.x, and even we release a 3.x version, i think almost no one would like to maintain the 3.x version.
IMHO, If we can guarantee full compatibility between the Hive4 and Hive3, why we still try to release the 3.x version?
The most important thing, since Hive4 has lots of bug fix & improvment & new features, we Hive community need to encourage people to use Hive4 and listen to the feedback & continue to optimize Hive4, and then people can always enjoy the up to date Hive4 version & this can also help the Hive community grow in a positive way.
I am +1 for marking 3.x EOL.
Thanks,
Butao Zhang
---- Replied Message ----
From
Ayush Saxena<ay...@gmail.com><mailto:undefined>
Date
9/28/2024 14:56
To
<de...@hive.apache.org>
Subject
Re: [DISCUSS] Hive 3.x release
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 candidate on PMC members who have no interest in this line
seems unfair. This approach feels counterproductive. Even if someone
were to take on the effort, it's unlikely others would participate in
the vote or review the RC, especially since few active contributors
(myself included) have been involved with 3.x. Requiring three binding
votes seems impractical under these circumstances.
I believe it's time to retire the 3.x line to address the recurring
security alerts we keep receiving. As far as I know, ending a release
line requires a majority vote from the PMC—more +1s than -1s. Based on
current sentiment, I believe most active PMC members would support
dropping 3.x.
-Ayush
On Sat, 28 Sept 2024 at 09:28, vihang karajgaonkar <vi...@apache.org>> wrote:
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 anymore. If not, we should consider if we can make a release out of branch-3 head.
Thanks,
Vihang
On Wed, Sep 25, 2024 at 2:57 PM Stamatis Zampetakis <za...@apache.org>> wrote:
Hi all,
Hive 3.1.3 was released on 2022-06-17 and it is the most recent
release of the 3.x line. Two years have passed since then and we still
don't have a new 3.x release. Claiming that we have support for the
3.x line and not getting releases out is hurting the project in
various ways.
I know that there has been some backporting activity on branch-3 but
personally I have no visibility on what is pending and what is the ETA
for the next release.
Is there a realistic plan that could get us a new release in the next
1-2 months?
Best,
Stamatis
[1] https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s
Re: [DISCUSS] Hive 3.x release
Posted by Simhadri G <si...@gmail.com>.
I agree with Ayush and Butao Zhang.
Hive 4 introduces numerous new features, critical bug and security fixes,
and significant performance improvements. Given that hive 4 has over 5000
commits compared to Hive 3, backporting changes from hive 4 to hive 3 would
be a tedious task due to high possibility of merge conflicts. I believe it
would be more productive to focus our active development efforts on the
latest master, rather than continuing to maintain and release Hive 3.
I am +1 for marking 3.x EOL.
Thanks!
Simhadri G
On Sat, Sep 28, 2024 at 1:29 PM Butao Zhang <bu...@163.com> wrote:
>
> Agreed with Ayush. I think we won't put much effort into 3.x, and even we
> release a 3.x version, i think almost no one would like to maintain the 3.x
> version.
> IMHO, If we can guarantee full compatibility between the Hive4 and Hive3,
> why we still try to release the 3.x version?
> The most important thing, since Hive4 has lots of bug fix & improvment &
> new features, we Hive community need to encourage people to use Hive4 and
> listen to the feedback & continue to optimize Hive4, and then people can
> always enjoy the up to date Hive4 version & this can also help the Hive
> community grow in a positive way.
>
> I am +1 for marking 3.x EOL.
>
>
>
> Thanks,
> Butao Zhang
> ---- Replied Message ----
> From Ayush Saxena<ay...@gmail.com> <undefined>
> Date 9/28/2024 14:56
> To <de...@hive.apache.org> <de...@hive.apache.org>
> Subject Re: [DISCUSS] Hive 3.x release
> 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 candidate on PMC members who have no interest in this line
> seems unfair. This approach feels counterproductive. Even if someone
> were to take on the effort, it's unlikely others would participate in
> the vote or review the RC, especially since few active contributors
> (myself included) have been involved with 3.x. Requiring three binding
> votes seems impractical under these circumstances.
>
> I believe it's time to retire the 3.x line to address the recurring
> security alerts we keep receiving. As far as I know, ending a release
> line requires a majority vote from the PMC—more +1s than -1s. Based on
> current sentiment, I believe most active PMC members would support
> dropping 3.x.
>
> -Ayush
>
> On Sat, 28 Sept 2024 at 09:28, vihang karajgaonkar <vi...@apache.org>
> wrote:
>
>
> 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 anymore. If not, we should consider if we can make a
> release out of branch-3 head.
>
> Thanks,
> Vihang
>
> On Wed, Sep 25, 2024 at 2:57 PM Stamatis Zampetakis <za...@apache.org>
> wrote:
>
>
> Hi all,
>
> Hive 3.1.3 was released on 2022-06-17 and it is the most recent
> release of the 3.x line. Two years have passed since then and we still
> don't have a new 3.x release. Claiming that we have support for the
> 3.x line and not getting releases out is hurting the project in
> various ways.
>
> I know that there has been some backporting activity on branch-3 but
> personally I have no visibility on what is pending and what is the ETA
> for the next release.
>
> Is there a realistic plan that could get us a new release in the next
> 1-2 months?
>
> Best,
> Stamatis
>
> [1] https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s
>
>
Re: [DISCUSS] Hive 3.x release
Posted by Butao Zhang <bu...@163.com>.
Agreed with Ayush. I think we won't put much effort into 3.x, and even we release a 3.x version, i think almost no one would like to maintain the 3.x version.
IMHO, If we can guarantee full compatibility between the Hive4 and Hive3, why we still try to release the 3.x version?
The most important thing, since Hive4 has lots of bug fix & improvment & new features, we Hive community need to encourage people to use Hive4 and listen to the feedback & continue to optimize Hive4, and then people can always enjoy the up to date Hive4 version & this can also help the Hive community grow in a positive way.
I am +1 for marking 3.x EOL.
Thanks,
Butao Zhang
---- Replied Message ----
| From | Ayush Saxena<ay...@gmail.com> |
| Date | 9/28/2024 14:56 |
| To | <de...@hive.apache.org> |
| Subject | Re: [DISCUSS] Hive 3.x release |
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 candidate on PMC members who have no interest in this line
seems unfair. This approach feels counterproductive. Even if someone
were to take on the effort, it's unlikely others would participate in
the vote or review the RC, especially since few active contributors
(myself included) have been involved with 3.x. Requiring three binding
votes seems impractical under these circumstances.
I believe it's time to retire the 3.x line to address the recurring
security alerts we keep receiving. As far as I know, ending a release
line requires a majority vote from the PMC—more +1s than -1s. Based on
current sentiment, I believe most active PMC members would support
dropping 3.x.
-Ayush
On Sat, 28 Sept 2024 at 09:28, vihang karajgaonkar <vi...@apache.org> wrote:
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 anymore. If not, we should consider if we can make a release out of branch-3 head.
Thanks,
Vihang
On Wed, Sep 25, 2024 at 2:57 PM Stamatis Zampetakis <za...@apache.org> wrote:
Hi all,
Hive 3.1.3 was released on 2022-06-17 and it is the most recent
release of the 3.x line. Two years have passed since then and we still
don't have a new 3.x release. Claiming that we have support for the
3.x line and not getting releases out is hurting the project in
various ways.
I know that there has been some backporting activity on branch-3 but
personally I have no visibility on what is pending and what is the ETA
for the next release.
Is there a realistic plan that could get us a new release in the next
1-2 months?
Best,
Stamatis
[1] https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s
Re: [DISCUSS] Hive 3.x release
Posted by Ayush Saxena <ay...@gmail.com>.
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 candidate on PMC members who have no interest in this line
seems unfair. This approach feels counterproductive. Even if someone
were to take on the effort, it's unlikely others would participate in
the vote or review the RC, especially since few active contributors
(myself included) have been involved with 3.x. Requiring three binding
votes seems impractical under these circumstances.
I believe it's time to retire the 3.x line to address the recurring
security alerts we keep receiving. As far as I know, ending a release
line requires a majority vote from the PMC—more +1s than -1s. Based on
current sentiment, I believe most active PMC members would support
dropping 3.x.
-Ayush
On Sat, 28 Sept 2024 at 09:28, vihang karajgaonkar <vi...@apache.org> wrote:
>
> 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 anymore. If not, we should consider if we can make a release out of branch-3 head.
>
> Thanks,
> Vihang
>
> On Wed, Sep 25, 2024 at 2:57 PM Stamatis Zampetakis <za...@apache.org> wrote:
>>
>> Hi all,
>>
>> Hive 3.1.3 was released on 2022-06-17 and it is the most recent
>> release of the 3.x line. Two years have passed since then and we still
>> don't have a new 3.x release. Claiming that we have support for the
>> 3.x line and not getting releases out is hurting the project in
>> various ways.
>>
>> I know that there has been some backporting activity on branch-3 but
>> personally I have no visibility on what is pending and what is the ETA
>> for the next release.
>>
>> Is there a realistic plan that could get us a new release in the next
>> 1-2 months?
>>
>> Best,
>> Stamatis
>>
>> [1] https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s
Re: [DISCUSS] Hive 3.x release
Posted by vihang karajgaonkar <vi...@apache.org>.
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 anymore. If not, we should consider if we can make a
release out of branch-3 head.
Thanks,
Vihang
On Wed, Sep 25, 2024 at 2:57 PM Stamatis Zampetakis <za...@apache.org>
wrote:
> Hi all,
>
> Hive 3.1.3 was released on 2022-06-17 and it is the most recent
> release of the 3.x line. Two years have passed since then and we still
> don't have a new 3.x release. Claiming that we have support for the
> 3.x line and not getting releases out is hurting the project in
> various ways.
>
> I know that there has been some backporting activity on branch-3 but
> personally I have no visibility on what is pending and what is the ETA
> for the next release.
>
> Is there a realistic plan that could get us a new release in the next
> 1-2 months?
>
> Best,
> Stamatis
>
> [1] https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s
>