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