Re: [DISCUSS] Hive 4.1.x release

I also think we can discuss when it turns out that we really need 4.1.1, for example, due to a critical CVE. Essentially, cherry-picking is not straightforward thanks to our recent excellent momentum and changes, such as JDK 21 or the restructuring of IMetaStoreClient. However, if it is genuinely e

Re: [DISCUSS] Hive 4.1.x release

+1 to initiating the discussions once this is wrapped up. That said, I echo the concerns raised by Stamatis — we simply don't have the resources or bandwidth to maintain multiple release lines. We shouldn't plan with 4.1.1 in mind from the outset. Instead, let’s keep the door open for a potential 4

Re: [DISCUSS] Hive 4.1.x release

Not sure. ideally, 4.1.1 should include the critical fixes. However, we might consider a major release that includes JDK 21 support, Iceberg auto-compaction, and other improvements from the master branch. But let’s discuss it once we get there.

Re: [DISCUSS] Hive 4.1.x release

els%20%3D%20hive-4.1.0-must%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC > [2] https://issues.apache.org/jira/browse/HIVE-29061 > [3] https://issues.apache.org/jira/browse/HIVE-29063 > > Thanks, > Butao Zhang > ---- Replied Message ---- > From Ayush Saxena > Date 7/

Re: [DISCUSS] Hive 4.1.x release

%20DESC%2C%20priority%20DESC [2] https://issues.apache.org/jira/browse/HIVE-29061 [3] https://issues.apache.org/jira/browse/HIVE-29063 Thanks, Butao Zhang Replied Message | From | Ayush Saxena | | Date | 7/8/2025 18:32 | | To | | | Subject | Re: [DISCUSS] Hive 4.1.x release | Hi Butao

Re: [DISCUSS] Hive 4.1.x release

Hi Butao, Just checking in — do you have any pointers on what’s still pending, or when we might expect to have an RC ready for vote? Are there any major blockers we should be aware of? Thanks, Ayush On Thu, 26 Jun 2025 at 00:02, Denys Kuzmenko wrote: > > I've updated the Release guide with instr

Re: [DISCUSS] Hive 4.1.x release

I've updated the Release guide with instructions for the HMS: https://github.com/apache/hive-site/pull/51

Re: [DISCUSS] Hive 4.1.x release

Replied Message | From | Attila Turoczy | | Date | 6/23/2025 19:47 | | To | | | Subject | Re: [DISCUSS] Hive 4.1.x release | In my view, Hive 5 (high five! 🙂) should represent a major milestone. Ideally, it would include more impactful changes such as: Making Iceberg the default table format

Re: [DISCUSS] Hive 4.1.x release

0.0/hive-standalone-metastore-3.0.0-bin.tar.gz > > > > > Thanks, > Butao Zhang > ---- Replied Message ---- > | From | Denys Kuzmenko | > | Date | 6/25/2025 02:26 | > | To | | > | Subject | Re: [DISCUSS] Hive 4.1.x release | > Would be nice to resolve > https://sonarcloud.io/project/issues?impactSeverities=BLOCKER&issueStatuses=OPEN%2CCONFIRMED&id=apache_hive > before the Hive-5.x release >

Re: [DISCUSS] Hive 4.1.x release

-metastore-4.1.0-SNAPSHOT-src.tar.gz [3] https://downloads.apache.org/hive/hive-standalone-metastore-3.0.0/hive-standalone-metastore-3.0.0-bin.tar.gz Thanks, Butao Zhang Replied Message | From | Denys Kuzmenko | | Date | 6/25/2025 02:26 | | To | | | Subject | Re: [DISCUSS] Hive 4.1.x r

Re: [DISCUSS] Hive 4.1.x release

Would be nice to resolve https://sonarcloud.io/project/issues?impactSeverities=BLOCKER&issueStatuses=OPEN%2CCONFIRMED&id=apache_hive before the Hive-5.x release

Re: [DISCUSS] Hive 4.1.x release

> From Attila Turoczy > > Date 6/23/2025 19:47 > To > Subject Re: [DISCUSS] Hive 4.1.x release > In my view, Hive 5 (high five! 🙂) should represent a major milestone. > Ideally, it would include more impactful changes such as: > >- Making Iceberg the

Re: [DISCUSS] Hive 4.1.x release

Having the 25th as the branch creation date sounds good to me. Regarding HIVE-29038 — if there's a quick fix available, I’m fine proceeding with it. Once the branch is created, we can wait for the DN regressions to be addressed there. In the meantime, any other fixes that land can also be cherry-p

Re: [DISCUSS] Hive 4.1.x release

Currently, at least three items remain incomplete: https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20hive-4.1.0-must%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC

Re: [DISCUSS] Hive 4.1.x release

5.x? > > > Replied Message > From Ayush Saxena > Date 06/23/2025 19:31 > To dev@hive.apache.org > Cc > Subject Re: [DISCUSS] Hive 4.1.x release > I don’t have a strict preference around the version number — the > important thing is that we get the release o

Re: [DISCUSS] Hive 4.1.x release

What if we integrate JDK 21 and then release version 5.x? Replied Message | From | Ayush Saxena | | Date | 06/23/2025 19:31 | | To | dev@hive.apache.org | | Cc | | | Subject | Re: [DISCUSS] Hive 4.1.x release | I don’t have a strict preference around the version number — the important

Re: [DISCUSS] Hive 4.1.x release

gt;> Perhaps we should initiate a community email vote on whether to name it >> 4.1.0 or 5.0.0? >> >> [1]https://lists.apache.org/thread/c166fz9hr3yft75qo3lcmhrbm1howpol >> >> Thanks, >> Butao Zhang >> Replied Message >> FromAyush Saxen

Re: [DISCUSS] Hive 4.1.x release

ao Zhang > Replied Message ---- > From Ayush Saxena > Date 6/23/2025 17:23 > To > Subject Re: [DISCUSS] Hive 4.1.x release > > Could we consider sending out a notification email? > > > Let’s have Butao Zhang, with their Release Manager hat on, do the > honor

Re: [DISCUSS] Hive 4.1.x release

Do we consider the two REST catalog issues as blockers? To me, they seem more like improvements that we could potentially defer, especially if the other item gets addressed. Denys — is HIVE-28744 a regression, or was it present in earlier releases too? The other two do appear to be blockers. Pers

Re: [DISCUSS] Hive 4.1.x release

HIVE-29038 is more like an open discussion. 25th sounds good! Could we consider sending out a notification email? Thanks!

Re: [DISCUSS] Hive 4.1.x release

ts.apache.org/thread/c166fz9hr3yft75qo3lcmhrbm1howpol Thanks, Butao Zhang Replied Message | From | Ayush Saxena | | Date | 6/23/2025 17:23 | | To | | | Subject | Re: [DISCUSS] Hive 4.1.x release | Could we consider sending out a notification email? Let’s have Butao Zhang, with their Release Ma

Re: [DISCUSS] Hive 4.1.x release

it through cherry-pick. Thanks, Butao Zhang Replied Message | From | Ayush Saxena | | Date | 6/23/2025 14:09 | | To | | | Subject | Re: [DISCUSS] Hive 4.1.x release | Do we consider the two REST catalog issues as blockers? To me, they seem more like improvements that we could

Re: [DISCUSS] Hive 4.1.x release

Hi Butao Zhang, I believe all blockers have now been addressed. The remaining items, as far as I can tell, are nice-to-haves rather than critical. You can go ahead with the branch creation and initiate the release process. If any pending items get resolved before the tag is pushed, they can sti

Re: [DISCUSS] Hive 4.1.x release

> Could we consider sending out a notification email? Let’s have Butao Zhang, with their Release Manager hat on, do the honors here. :-) Butao Zhang, could you please send out a [NOTICE] email announcing that the code freeze for 4.1.0 is set for the 25th? Post that, only critical items will be co

Re: [DISCUSS] Hive 4.1.x release

It's great to see that we are so close in cutting the next Hive release! My take as usual is to not hold off the release unless there are serious issues, regressions, and legally blocking stuff. Anything that falls into the category nice to have can go into the next release assuming that it will f

Re: [DISCUSS] Hive 4.1.x release

RestCatalog is definitely not a blocker, however, would be good to reach an agreement on HIVE-29038 before releasing the new configs. For now, we can move forward with Iceberg-specific configs and handle unification in a follow-up release. WDYT? HIVE-28744

Re: Re: [DISCUSS] Hive 4.1.x release

Thanks Denys! I am also watching these tickets. On 2025/06/19 09:32:28 Denys Kuzmenko wrote: > Hi everyone, > > Short Status UPDATE: > > RESOLVED: > 1) HIVE-28987 : Iceberg: A > faulty query predicate can compromise transaction isolation. > 2) H

Re: Re: [DISCUSS] Hive 4.1.x release

Hi everyone, Short Status UPDATE: RESOLVED: 1) HIVE-28987 : Iceberg: A faulty query predicate can compromise transaction isolation. 2) HIVE-27275 : Provide docker image for HMS 3) HIVE-28665

Re: Re: [DISCUSS] Hive 4.1.x release

I just added hive-4.1.0-must label on a recently created HIVE-29003 : DatePartitionedLogger from Tez is always needed for hive logging hook, please consider this also On Mon, 9 Jun 2025 at 14:33, Okumin wrote: > Hi, > > I plan to test "HIVE-28059

Re: Re: [DISCUSS] Hive 4.1.x release

Hi, I plan to test "HIVE-28059: Iceberg REST Catalog" via another query engine quickly once Iceberg 1.9.1 is merged. When I tested it last time, a set of basic commands didn't work because our HiveCatalog lacked some features. Now, it should be ok. I'm also aware that the current REST Catalog only

Re: Re: [DISCUSS] Hive 4.1.x release

Hi, If we are adding standalone-metastore docker image, i think it will be good to add a github action to build and push this image to hive dockerhub repo as well. Thanks! Simhadri G On Mon, Jun 9, 2025 at 2:44 P

Re: Re: [DISCUSS] Hive 4.1.x release

Hi, We reviewed and cleaned up the `hive-must` items with Ayush. A few tasks remain, which should be resolved soon, along with some pending responses. Regarding the `standalone-metastore`, I suggest releasing a tarball and a lightweight Docker image, as there has been strong interest. I plan t

Re: Re: [DISCUSS] Hive 4.1.x release

I'm very glad to see that the jdk17 issues related to the version 4.1.0 have been resolved. As the release manager of version 4.1.0, I have studied the documentation for hive version releases[1]. I think the next step is to cut the 4.1.0 branch from the master branch. From the PRs mentioned b

Re: Re: [DISCUSS] Hive 4.1.x release

The following filter returns 17 'hive-4.1.0-must' items, some with the abandon PR: https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20%3D%20hive-4.1.0-must%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC

Re: Re: [DISCUSS] Hive 4.1.x release

Hi Team! If we consider non-blockers too (idea came from Denys' suggestion above), then I would love to include these below (both are 99% finished/approved, I'm just fighting with the precommit): 1. HIVE-28930 : Implement a metastore servic

Re: Re: [DISCUSS] Hive 4.1.x release

Hi Ayush, Thanks for restarting the conversation! I have a few additional items to consider, with only the first one being mandatory. 1) HIVE-28987: Iceberg: A faulty query predicate can compromise transaction isolation. 2) HIVE-27275: Provide docker image for HMS (needs approving review) 3)

Re: Re: [DISCUSS] Hive 4.1.x release

1.0, please add hive-4.1.0-must label in > > > the JIRA. Some open tickets for 4.1.0 list in [1]. > > > > > > [1] > > > https://issues.apache.org/jira/browse/HIVE-28669?jql=status%20in%20(Open%2C%20%22In%20Progress%22)%20AND%20labels%20%3D%20hive-4.1.0-must > &

Re: Re: [DISCUSS] Hive 4.1.x release

rogress%22)%20AND%20labels%20%3D%20hive-4.1.0-must > > > > > > Thanks, > > Butao Zhang > > Replied Message > > From Stamatis Zampetakis > > Date 12/16/2024 17:33 > > To > > Subject Re: Re: [DISCUSS] Hive 4.1.x release > > The master

Re: Re: [DISCUSS] Hive 4.1.x release

] > https://issues.apache.org/jira/browse/HIVE-28669?jql=status%20in%20(Open%2C%20%22In%20Progress%22)%20AND%20labels%20%3D%20hive-4.1.0-must > > > Thanks, > Butao Zhang > Replied Message > From Stamatis Zampetakis > Date 12/16/2024 17:33 > To > Subject Re:

Re: Re: [DISCUSS] Hive 4.1.x release

| From | Stamatis Zampetakis | | Date | 12/16/2024 17:33 | | To | | | Subject | Re: Re: [DISCUSS] Hive 4.1.x release | The master branch has enough content to justify a release and make many end-users happy. The naming depends (4.1.0, 4.0.2, 5.0.0) on the actual content and without doing an exhaustive

Re: Re: [DISCUSS] Hive 4.1.x release

The master branch has enough content to justify a release and make many end-users happy. The naming depends (4.1.0, 4.0.2, 5.0.0) on the actual content and without doing an exhaustive check I feel that if we release now we should do a minor bump i.e., 4.1.0. If we start compiling with JDK17, it is

Re:Re: [DISCUSS] Hive 4.1.x release

I agree with Butao that since the community has previously promised that jdk17 will be supported in 4.1.0, it would be best if we keep that promise. But maybe we can go ahead and release a 4.0.2 version?And then wait for HIVE-28665 to be merged before releasing a 4.1.0 version? At

Re: [DISCUSS] Hive 4.1.x release

Thanks Stamatis for your insightful suggestion! I basically agree with you, and what you said is also what i have been thinking recently. However, i think we've had a lot of discussion about the release of jdk17 features in version Hive 4.1.x. At some point, many community users will expect Hiv

Re: [DISCUSS] Hive 4.1.x release

Thanks for volunteering Butao! As usual I have a slightly different perspective regarding the scope for the release. If there are no regressions or other serious blockers in the current master we could cut the release ASAP. We don't need to delay the release for getting new features in. Once JDK-1

Re: [DISCUSS] Hive 4.1.x release

Hi Team, Thanks for the productive discussion! I’d like to provide a quick update on JDK-17. The initial review comments have been addressed, and to stay aligned with ongoing upstream changes, we’ve rebased the PR onto the latest master. After the recent rebase, we did encounter multiple test fail

Re: [DISCUSS] Hive 4.1.x release

Thanks! IMO, JDK-17(HIVE-26473) should definitely be included in this release. I am also watching it. Maybe we can cut the branch-4.1 at some point after the JDK-17 is finished. Thanks, Butao Zhang On 2024/12/11 14:22:55 Denys Kuzmenko wrote: > Thanks Butao! > We'll support you all the way.

Re: [DISCUSS] Hive 4.1.x release

Thanks Butao! We'll support you all the way. ATM we should probably finalize the scope for the release (create new label hive-4.1.0-must) and focus of getting those items prioritised. There is also ongoing discussion on JDK-8 and JDK-17. Would be great if we manage to add support for JDK-17 i

Re: [DISCUSS] Hive 4.1.x release

Hi, We have a wiki for the release process: https://cwiki.apache.org/confluence/display/Hive/HowToRelease -Ayush > On 11 Dec 2024, at 4:03 PM, Butao Zhang wrote: > > Hi, Denys: > >Good to know Hive 4.1.x is coming soon! I can be the volunteer to make > Hive 4.1.x release happen. Coul

Re: [DISCUSS] Hive 4.1.x release

Hi, Denys: Good to know Hive 4.1.x is coming soon! I can be the volunteer to make Hive 4.1.x release happen. Could you share some information about the release process? I want to learn the release process in advance. Thanks, Butao Zhang On 2024/12/10 09:33:19 Denys Kuzmenko wrote: >

[DISCUSS] Hive 4.1.x release

Hi All, It's time we start prepping for the next release. Since Hive 4.0 was cut, a number of bug-fixes, features, and performance improvements landed in the master. We are looking for a volunteer (Committer / PMC) to fill the role of the next Release Manager. Thanks, Denys