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" <ayush...@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 <raja...@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 <vihan...@apache.org> >> Sent: Saturday, October 5, 2024 11:07:36 AM >> To: dev@hive.apache.org <dev@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 <zabe...@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 <vihan...@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 <ayush...@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 <dkuzme...@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.
