You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Kirti Ruge <ki...@gmail.com> on 2023/03/08 09:02:11 UTC
[DISCUSS] HIVE 4.0 GA Release Proposal
Hello Hive Dev,
It has been about 6 months since Hive-4.0-alpha-2 was released in Nov 2022.
Would it be a good time to discuss about HIVE-4.0 GA release to the community ? Can we have discussion on the new features/jdk support versions which we want to publish as part of 4.0 GA , timeframe of release.
Thanks,
Kirti
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Hi Stamatis,
Any further update on the following which we missed here. thanks
Regards,
Brahma.
From: Stamatis Zampetakis <za...@gmail.com>
Date: Tuesday, August 1, 2023 at 17:05
To: dev@hive.apache.org <de...@hive.apache.org>
Subject: Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Hello,
HIVE-27504 is now merged to master. Thanks everyone for the reviews!
I am going to prepare the release candidate for 4.0.0-beta-1 sometime this week.
Best,
Stamatis
On Thu, Jul 27, 2023 at 1:54 PM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> Looks following PR is reviewed. Any chance to get it merged and give the release.?
>
> On 18/07/23, 2:39 PM, "Stamatis Zampetakis" <zabetak@gmail.com <ma...@gmail.com>> wrote:
>
>
> HIVE-27504 still lacks reviews from committers.
>
>
> Note that I will not be able to work on the release from 22/07 to
> 30/07. If HIVE-27504 does not land in the next day or two the beta-1
> release might get delayed unless someone else picks up the RM role and
> cuts the RC.
>
>
> Best,
> Stamatis
>
>
> On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
> <aturoczy@cloudera.com.inva <ma...@cloudera.com.inva>lid<mailto:aturoczy@cloudera.com.inva%3elid>> wrote:
> >
> > Thanks for the update! Can't wait for the beta :)
> >
> > -Attila
> >
> > On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis <zabetak@gmail.com <ma...@gmail.com>>
> > wrote:
> >
> > > Hey everyone,
> > >
> > > As you may have noticed there have been various tickets around LICENSE
> > > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > > which hopefully addresses all remaining issues that were found while I
> > > was working with the RC. After this gets resolved we should be good to
> > > go for putting up the RC for vote.
> > >
> > > The structure and content of the LICENSE and NOTICE file are very
> > > important for Apache releases so I would encourage other members of
> > > the community (especially PMC) to review the latest changes and
> > > current status and raise new JIRA tickets if they discover some
> > > problems. I would like to avoid having last minute -1 votes due to
> > > that.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-27504&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jYi7uYaZRu7DeTziITt3tsrJsq605SYZdrVzC594580%3D&reserved=0<https://issues.apache.org/jira/browse/HIVE-27504> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-27504&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jYi7uYaZRu7DeTziITt3tsrJsq605SYZdrVzC594580%3D&reserved=0<https://issues.apache.org/jira/browse/HIVE-27504>>
> > >
> > > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis <zabetak@gmail.com <ma...@gmail.com>>
> > > wrote:
> > > >
> > > > Hey team,
> > > >
> > > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > > >
> > > > Most of the release steps went out smoothly and I was able to get an
> > > > RC0 ready [1].
> > > >
> > > > However, I am afraid that our binary distribution does not comply
> > > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > > within and I am not sure if we are fully covered in terms of licenses
> > > > and notice files. Thanks Ayush for reminding me to check the
> > > > binary-package-licenses directory [5].
> > > >
> > > > I am checking various resources such as [3, 4] to see what additional
> > > > steps we can take to be on the safe side and also looking for ways to
> > > > automate this so that we don't have to manually inspect the jars on
> > > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > > am not yet completely happy with its output.
> > > >
> > > > The next few days will be a bit busy so most likely I will get back on
> > > > this during the weekend. If people have feedback or other ideas to
> > > > share please let me know.
> > > >
> > > > Best,
> > > > Stamatis
> > > >
> > > > [1] https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeople.apache.org%2F~zabetak%2Fapache-hive-4.0.0-beta-1-rc0%2F&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cR6qbsbhYG3XgPMz77CEf7lfWyTM7Q0KJJVtnZ5ROJA%3D&reserved=0<https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeople.apache.org%2F~zabetak%2Fapache-hive-4.0.0-beta-1-rc0%2F&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cR6qbsbhYG3XgPMz77CEf7lfWyTM7Q0KJJVtnZ5ROJA%3D&reserved=0<https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/>>
> > > > [2]
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fsrc-headers.html%23asf-source-header-and-copyright-notice-policy&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pmoy6NplezTCZwAZsBSg2xVaM3ilAHqqzNNFr2UcF3A%3D&reserved=0<https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fsrc-headers.html%23asf-source-header-and-copyright-notice-policy&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pmoy6NplezTCZwAZsBSg2xVaM3ilAHqqzNNFr2UcF3A%3D&reserved=0<https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy>>
> > > > [3] https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Finfra.apache.org%2Flicensing-howto.html&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8lAiUyT2bvUX4JHKS%2FU%2FHIVLWI0AHHyAoIgjkpuPZ6U%3D&reserved=0<https://infra.apache.org/licensing-howto.html> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Finfra.apache.org%2Flicensing-howto.html&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8lAiUyT2bvUX4JHKS%2FU%2FHIVLWI0AHHyAoIgjkpuPZ6U%3D&reserved=0<https://infra.apache.org/licensing-howto.html>>
> > > > [4] https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GQBsjh86wI0bXpwpC0E4kTXen0NAgPo5DtfB%2B7OcIT4%3D&reserved=0<https://www.apache.org/legal/resolved.html> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GQBsjh86wI0bXpwpC0E4kTXen0NAgPo5DtfB%2B7OcIT4%3D&reserved=0<https://www.apache.org/legal/resolved.html>>
> > > > [5] https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fhive%2Ftree%2Fmaster%2Fbinary-package-licenses&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J1fLPdHd1jE03r4XZ5V1U6dt981H7vPlhvtfEvSPN%2BA%3D&reserved=0<https://github.com/apache/hive/tree/master/binary-package-licenses> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fhive%2Ftree%2Fmaster%2Fbinary-package-licenses&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J1fLPdHd1jE03r4XZ5V1U6dt981H7vPlhvtfEvSPN%2BA%3D&reserved=0<https://github.com/apache/hive/tree/master/binary-package-licenses>>
> > > > [6] https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mojohaus.org%2Flicense-maven-plugin%2F&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1ggxeyJmt77VjfXEy1xVmHCP%2BuP1tlDVZz%2FejerFHqM%3D&reserved=0<https://www.mojohaus.org/license-maven-plugin/> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mojohaus.org%2Flicense-maven-plugin%2F&data=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1ggxeyJmt77VjfXEy1xVmHCP%2BuP1tlDVZz%2FejerFHqM%3D&reserved=0<https://www.mojohaus.org/license-maven-plugin/>>
> > > >
> > > >
> > > > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis <zabetak@gmail.com <ma...@gmail.com>>
> > > wrote:
> > > > >
> > > > > I can start preparing the RC towards the end of next week. If somebody
> > > > > has more time and wants to start earlier I am fine to switch.
> > > > >
> > > > > Best,
> > > > > Stamatis
> > > > >
> > > > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko <dkuzmenko@apache.org <ma...@apache.org>>
> > > wrote:
> > > > > >
> > > > > > great, this is the current list of release managers:
> > > > > >
> > > > > > 4.0.0 Stamatis Zampetakis
> > > > > > 4.1.0 Denys Kuzmenko
> > > > > > 4.2.0 Sai Hemanth Gantasala
> > > > > >
> > > > > > Should we keep the same RM order and just shift the releases or find
> > > a volunteer for the 4.0.0-beta release, WDYT?
> > > > > >
> > > > > >
> > >
>
>
>
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
Hello,
HIVE-27504 is now merged to master. Thanks everyone for the reviews!
I am going to prepare the release candidate for 4.0.0-beta-1 sometime this week.
Best,
Stamatis
On Thu, Jul 27, 2023 at 1:54 PM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> Looks following PR is reviewed. Any chance to get it merged and give the release.?
>
> On 18/07/23, 2:39 PM, "Stamatis Zampetakis" <zabetak@gmail.com <ma...@gmail.com>> wrote:
>
>
> HIVE-27504 still lacks reviews from committers.
>
>
> Note that I will not be able to work on the release from 22/07 to
> 30/07. If HIVE-27504 does not land in the next day or two the beta-1
> release might get delayed unless someone else picks up the RM role and
> cuts the RC.
>
>
> Best,
> Stamatis
>
>
> On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
> <aturoczy@cloudera.com.inva <ma...@cloudera.com.inva>lid> wrote:
> >
> > Thanks for the update! Can't wait for the beta :)
> >
> > -Attila
> >
> > On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis <zabetak@gmail.com <ma...@gmail.com>>
> > wrote:
> >
> > > Hey everyone,
> > >
> > > As you may have noticed there have been various tickets around LICENSE
> > > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > > which hopefully addresses all remaining issues that were found while I
> > > was working with the RC. After this gets resolved we should be good to
> > > go for putting up the RC for vote.
> > >
> > > The structure and content of the LICENSE and NOTICE file are very
> > > important for Apache releases so I would encourage other members of
> > > the community (especially PMC) to review the latest changes and
> > > current status and raise new JIRA tickets if they discover some
> > > problems. I would like to avoid having last minute -1 votes due to
> > > that.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] https://issues.apache.org/jira/browse/HIVE-27504 <https://issues.apache.org/jira/browse/HIVE-27504>
> > >
> > > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis <zabetak@gmail.com <ma...@gmail.com>>
> > > wrote:
> > > >
> > > > Hey team,
> > > >
> > > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > > >
> > > > Most of the release steps went out smoothly and I was able to get an
> > > > RC0 ready [1].
> > > >
> > > > However, I am afraid that our binary distribution does not comply
> > > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > > within and I am not sure if we are fully covered in terms of licenses
> > > > and notice files. Thanks Ayush for reminding me to check the
> > > > binary-package-licenses directory [5].
> > > >
> > > > I am checking various resources such as [3, 4] to see what additional
> > > > steps we can take to be on the safe side and also looking for ways to
> > > > automate this so that we don't have to manually inspect the jars on
> > > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > > am not yet completely happy with its output.
> > > >
> > > > The next few days will be a bit busy so most likely I will get back on
> > > > this during the weekend. If people have feedback or other ideas to
> > > > share please let me know.
> > > >
> > > > Best,
> > > > Stamatis
> > > >
> > > > [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/ <https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/>
> > > > [2]
> > > https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy <https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy>
> > > > [3] https://infra.apache.org/licensing-howto.html <https://infra.apache.org/licensing-howto.html>
> > > > [4] https://www.apache.org/legal/resolved.html <https://www.apache.org/legal/resolved.html>
> > > > [5] https://github.com/apache/hive/tree/master/binary-package-licenses <https://github.com/apache/hive/tree/master/binary-package-licenses>
> > > > [6] https://www.mojohaus.org/license-maven-plugin/ <https://www.mojohaus.org/license-maven-plugin/>
> > > >
> > > >
> > > > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis <zabetak@gmail.com <ma...@gmail.com>>
> > > wrote:
> > > > >
> > > > > I can start preparing the RC towards the end of next week. If somebody
> > > > > has more time and wants to start earlier I am fine to switch.
> > > > >
> > > > > Best,
> > > > > Stamatis
> > > > >
> > > > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko <dkuzmenko@apache.org <ma...@apache.org>>
> > > wrote:
> > > > > >
> > > > > > great, this is the current list of release managers:
> > > > > >
> > > > > > 4.0.0 Stamatis Zampetakis
> > > > > > 4.1.0 Denys Kuzmenko
> > > > > > 4.2.0 Sai Hemanth Gantasala
> > > > > >
> > > > > > Should we keep the same RM order and just shift the releases or find
> > > a volunteer for the 4.0.0-beta release, WDYT?
> > > > > >
> > > > > >
> > >
>
>
>
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Looks following PR is reviewed. Any chance to get it merged and give the release.?
On 18/07/23, 2:39 PM, "Stamatis Zampetakis" <zabetak@gmail.com <ma...@gmail.com>> wrote:
HIVE-27504 still lacks reviews from committers.
Note that I will not be able to work on the release from 22/07 to
30/07. If HIVE-27504 does not land in the next day or two the beta-1
release might get delayed unless someone else picks up the RM role and
cuts the RC.
Best,
Stamatis
On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
<aturoczy@cloudera.com.inva <ma...@cloudera.com.inva>lid> wrote:
>
> Thanks for the update! Can't wait for the beta :)
>
> -Attila
>
> On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis <zabetak@gmail.com <ma...@gmail.com>>
> wrote:
>
> > Hey everyone,
> >
> > As you may have noticed there have been various tickets around LICENSE
> > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > which hopefully addresses all remaining issues that were found while I
> > was working with the RC. After this gets resolved we should be good to
> > go for putting up the RC for vote.
> >
> > The structure and content of the LICENSE and NOTICE file are very
> > important for Apache releases so I would encourage other members of
> > the community (especially PMC) to review the latest changes and
> > current status and raise new JIRA tickets if they discover some
> > problems. I would like to avoid having last minute -1 votes due to
> > that.
> >
> > Best,
> > Stamatis
> >
> > [1] https://issues.apache.org/jira/browse/HIVE-27504 <https://issues.apache.org/jira/browse/HIVE-27504>
> >
> > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis <zabetak@gmail.com <ma...@gmail.com>>
> > wrote:
> > >
> > > Hey team,
> > >
> > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > >
> > > Most of the release steps went out smoothly and I was able to get an
> > > RC0 ready [1].
> > >
> > > However, I am afraid that our binary distribution does not comply
> > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > within and I am not sure if we are fully covered in terms of licenses
> > > and notice files. Thanks Ayush for reminding me to check the
> > > binary-package-licenses directory [5].
> > >
> > > I am checking various resources such as [3, 4] to see what additional
> > > steps we can take to be on the safe side and also looking for ways to
> > > automate this so that we don't have to manually inspect the jars on
> > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > am not yet completely happy with its output.
> > >
> > > The next few days will be a bit busy so most likely I will get back on
> > > this during the weekend. If people have feedback or other ideas to
> > > share please let me know.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/ <https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/>
> > > [2]
> > https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy <https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy>
> > > [3] https://infra.apache.org/licensing-howto.html <https://infra.apache.org/licensing-howto.html>
> > > [4] https://www.apache.org/legal/resolved.html <https://www.apache.org/legal/resolved.html>
> > > [5] https://github.com/apache/hive/tree/master/binary-package-licenses <https://github.com/apache/hive/tree/master/binary-package-licenses>
> > > [6] https://www.mojohaus.org/license-maven-plugin/ <https://www.mojohaus.org/license-maven-plugin/>
> > >
> > >
> > > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis <zabetak@gmail.com <ma...@gmail.com>>
> > wrote:
> > > >
> > > > I can start preparing the RC towards the end of next week. If somebody
> > > > has more time and wants to start earlier I am fine to switch.
> > > >
> > > > Best,
> > > > Stamatis
> > > >
> > > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko <dkuzmenko@apache.org <ma...@apache.org>>
> > wrote:
> > > > >
> > > > > great, this is the current list of release managers:
> > > > >
> > > > > 4.0.0 Stamatis Zampetakis
> > > > > 4.1.0 Denys Kuzmenko
> > > > > 4.2.0 Sai Hemanth Gantasala
> > > > >
> > > > > Should we keep the same RM order and just shift the releases or find
> > a volunteer for the 4.0.0-beta release, WDYT?
> > > > >
> > > > >
> >
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
HIVE-27504 still lacks reviews from committers.
Note that I will not be able to work on the release from 22/07 to
30/07. If HIVE-27504 does not land in the next day or two the beta-1
release might get delayed unless someone else picks up the RM role and
cuts the RC.
Best,
Stamatis
On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
<at...@cloudera.com.invalid> wrote:
>
> Thanks for the update! Can't wait for the beta :)
>
> -Attila
>
> On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis <za...@gmail.com>
> wrote:
>
> > Hey everyone,
> >
> > As you may have noticed there have been various tickets around LICENSE
> > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > which hopefully addresses all remaining issues that were found while I
> > was working with the RC. After this gets resolved we should be good to
> > go for putting up the RC for vote.
> >
> > The structure and content of the LICENSE and NOTICE file are very
> > important for Apache releases so I would encourage other members of
> > the community (especially PMC) to review the latest changes and
> > current status and raise new JIRA tickets if they discover some
> > problems. I would like to avoid having last minute -1 votes due to
> > that.
> >
> > Best,
> > Stamatis
> >
> > [1] https://issues.apache.org/jira/browse/HIVE-27504
> >
> > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis <za...@gmail.com>
> > wrote:
> > >
> > > Hey team,
> > >
> > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > >
> > > Most of the release steps went out smoothly and I was able to get an
> > > RC0 ready [1].
> > >
> > > However, I am afraid that our binary distribution does not comply
> > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > within and I am not sure if we are fully covered in terms of licenses
> > > and notice files. Thanks Ayush for reminding me to check the
> > > binary-package-licenses directory [5].
> > >
> > > I am checking various resources such as [3, 4] to see what additional
> > > steps we can take to be on the safe side and also looking for ways to
> > > automate this so that we don't have to manually inspect the jars on
> > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > am not yet completely happy with its output.
> > >
> > > The next few days will be a bit busy so most likely I will get back on
> > > this during the weekend. If people have feedback or other ideas to
> > > share please let me know.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/
> > > [2]
> > https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
> > > [3] https://infra.apache.org/licensing-howto.html
> > > [4] https://www.apache.org/legal/resolved.html
> > > [5] https://github.com/apache/hive/tree/master/binary-package-licenses
> > > [6] https://www.mojohaus.org/license-maven-plugin/
> > >
> > >
> > > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis <za...@gmail.com>
> > wrote:
> > > >
> > > > I can start preparing the RC towards the end of next week. If somebody
> > > > has more time and wants to start earlier I am fine to switch.
> > > >
> > > > Best,
> > > > Stamatis
> > > >
> > > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko <dk...@apache.org>
> > wrote:
> > > > >
> > > > > great, this is the current list of release managers:
> > > > >
> > > > > 4.0.0 Stamatis Zampetakis
> > > > > 4.1.0 Denys Kuzmenko
> > > > > 4.2.0 Sai Hemanth Gantasala
> > > > >
> > > > > Should we keep the same RM order and just shift the releases or find
> > a volunteer for the 4.0.0-beta release, WDYT?
> > > > >
> > > > >
> >
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Attila Turoczy <at...@cloudera.com.INVALID>.
Thanks for the update! Can't wait for the beta :)
-Attila
On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis <za...@gmail.com>
wrote:
> Hey everyone,
>
> As you may have noticed there have been various tickets around LICENSE
> and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> which hopefully addresses all remaining issues that were found while I
> was working with the RC. After this gets resolved we should be good to
> go for putting up the RC for vote.
>
> The structure and content of the LICENSE and NOTICE file are very
> important for Apache releases so I would encourage other members of
> the community (especially PMC) to review the latest changes and
> current status and raise new JIRA tickets if they discover some
> problems. I would like to avoid having last minute -1 votes due to
> that.
>
> Best,
> Stamatis
>
> [1] https://issues.apache.org/jira/browse/HIVE-27504
>
> On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis <za...@gmail.com>
> wrote:
> >
> > Hey team,
> >
> > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> >
> > Most of the release steps went out smoothly and I was able to get an
> > RC0 ready [1].
> >
> > However, I am afraid that our binary distribution does not comply
> > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > within and I am not sure if we are fully covered in terms of licenses
> > and notice files. Thanks Ayush for reminding me to check the
> > binary-package-licenses directory [5].
> >
> > I am checking various resources such as [3, 4] to see what additional
> > steps we can take to be on the safe side and also looking for ways to
> > automate this so that we don't have to manually inspect the jars on
> > every release. I was playing a bit with license-maven-plugin [6] but I
> > am not yet completely happy with its output.
> >
> > The next few days will be a bit busy so most likely I will get back on
> > this during the weekend. If people have feedback or other ideas to
> > share please let me know.
> >
> > Best,
> > Stamatis
> >
> > [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/
> > [2]
> https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
> > [3] https://infra.apache.org/licensing-howto.html
> > [4] https://www.apache.org/legal/resolved.html
> > [5] https://github.com/apache/hive/tree/master/binary-package-licenses
> > [6] https://www.mojohaus.org/license-maven-plugin/
> >
> >
> > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis <za...@gmail.com>
> wrote:
> > >
> > > I can start preparing the RC towards the end of next week. If somebody
> > > has more time and wants to start earlier I am fine to switch.
> > >
> > > Best,
> > > Stamatis
> > >
> > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko <dk...@apache.org>
> wrote:
> > > >
> > > > great, this is the current list of release managers:
> > > >
> > > > 4.0.0 Stamatis Zampetakis
> > > > 4.1.0 Denys Kuzmenko
> > > > 4.2.0 Sai Hemanth Gantasala
> > > >
> > > > Should we keep the same RM order and just shift the releases or find
> a volunteer for the 4.0.0-beta release, WDYT?
> > > >
> > > >
>
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
Hey everyone,
As you may have noticed there have been various tickets around LICENSE
and NOTICE files popping up recently. I just logged HIVE-27504 [1]
which hopefully addresses all remaining issues that were found while I
was working with the RC. After this gets resolved we should be good to
go for putting up the RC for vote.
The structure and content of the LICENSE and NOTICE file are very
important for Apache releases so I would encourage other members of
the community (especially PMC) to review the latest changes and
current status and raise new JIRA tickets if they discover some
problems. I would like to avoid having last minute -1 votes due to
that.
Best,
Stamatis
[1] https://issues.apache.org/jira/browse/HIVE-27504
On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis <za...@gmail.com> wrote:
>
> Hey team,
>
> Small heads up regarding the progress of the 4.0.0-beta-1 release.
>
> Most of the release steps went out smoothly and I was able to get an
> RC0 ready [1].
>
> However, I am afraid that our binary distribution does not comply
> fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> within and I am not sure if we are fully covered in terms of licenses
> and notice files. Thanks Ayush for reminding me to check the
> binary-package-licenses directory [5].
>
> I am checking various resources such as [3, 4] to see what additional
> steps we can take to be on the safe side and also looking for ways to
> automate this so that we don't have to manually inspect the jars on
> every release. I was playing a bit with license-maven-plugin [6] but I
> am not yet completely happy with its output.
>
> The next few days will be a bit busy so most likely I will get back on
> this during the weekend. If people have feedback or other ideas to
> share please let me know.
>
> Best,
> Stamatis
>
> [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/
> [2] https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
> [3] https://infra.apache.org/licensing-howto.html
> [4] https://www.apache.org/legal/resolved.html
> [5] https://github.com/apache/hive/tree/master/binary-package-licenses
> [6] https://www.mojohaus.org/license-maven-plugin/
>
>
> On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis <za...@gmail.com> wrote:
> >
> > I can start preparing the RC towards the end of next week. If somebody
> > has more time and wants to start earlier I am fine to switch.
> >
> > Best,
> > Stamatis
> >
> > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko <dk...@apache.org> wrote:
> > >
> > > great, this is the current list of release managers:
> > >
> > > 4.0.0 Stamatis Zampetakis
> > > 4.1.0 Denys Kuzmenko
> > > 4.2.0 Sai Hemanth Gantasala
> > >
> > > Should we keep the same RM order and just shift the releases or find a volunteer for the 4.0.0-beta release, WDYT?
> > >
> > >
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
Hey team,
Small heads up regarding the progress of the 4.0.0-beta-1 release.
Most of the release steps went out smoothly and I was able to get an
RC0 ready [1].
However, I am afraid that our binary distribution does not comply
fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
within and I am not sure if we are fully covered in terms of licenses
and notice files. Thanks Ayush for reminding me to check the
binary-package-licenses directory [5].
I am checking various resources such as [3, 4] to see what additional
steps we can take to be on the safe side and also looking for ways to
automate this so that we don't have to manually inspect the jars on
every release. I was playing a bit with license-maven-plugin [6] but I
am not yet completely happy with its output.
The next few days will be a bit busy so most likely I will get back on
this during the weekend. If people have feedback or other ideas to
share please let me know.
Best,
Stamatis
[1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/
[2] https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
[3] https://infra.apache.org/licensing-howto.html
[4] https://www.apache.org/legal/resolved.html
[5] https://github.com/apache/hive/tree/master/binary-package-licenses
[6] https://www.mojohaus.org/license-maven-plugin/
On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis <za...@gmail.com> wrote:
>
> I can start preparing the RC towards the end of next week. If somebody
> has more time and wants to start earlier I am fine to switch.
>
> Best,
> Stamatis
>
> On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko <dk...@apache.org> wrote:
> >
> > great, this is the current list of release managers:
> >
> > 4.0.0 Stamatis Zampetakis
> > 4.1.0 Denys Kuzmenko
> > 4.2.0 Sai Hemanth Gantasala
> >
> > Should we keep the same RM order and just shift the releases or find a volunteer for the 4.0.0-beta release, WDYT?
> >
> >
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
I can start preparing the RC towards the end of next week. If somebody
has more time and wants to start earlier I am fine to switch.
Best,
Stamatis
On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko <dk...@apache.org> wrote:
>
> great, this is the current list of release managers:
>
> 4.0.0 Stamatis Zampetakis
> 4.1.0 Denys Kuzmenko
> 4.2.0 Sai Hemanth Gantasala
>
> Should we keep the same RM order and just shift the releases or find a volunteer for the 4.0.0-beta release, WDYT?
>
>
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Denys Kuzmenko <dk...@apache.org>.
great, this is the current list of release managers:
4.0.0 Stamatis Zampetakis
4.1.0 Denys Kuzmenko
4.2.0 Sai Hemanth Gantasala
Should we keep the same RM order and just shift the releases or find a volunteer for the 4.0.0-beta release, WDYT?
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Ayush Saxena <ay...@gmail.com>.
+1, for a pre GA release
Beta sounds better to me, we don’t have any half baked major features, just
probabilities of some bugs
-Ayush
On Thu, 1 Jun 2023 at 4:24 PM, Attila Turoczy <at...@cloudera.com.invalid>
wrote:
> Ayush just told me, the mailing list does not support images. It is a very
> sad world :-(
>
> Previous meme:
> https://imgflip.com/i/7nuzql
>
> On Thu, Jun 1, 2023 at 11:46 AM Attila Turoczy <at...@cloudera.com>
> wrote:
>
>> OK. Then let's go with beta. Please start. (if not started already) a
>> vote for a release.
>>
>> I think we should have a more frequent release cadence. The community
>> needs it, we need this, also without frequent release nobody will believe
>> this project is healthy. I know the first will be the hardest, but we need
>> to fix those issues and release them. Even a monthly release could be
>> possible for hive. We are capable to do this!
>>
>> [image: image.png]
>>
>> -Attila
>>
>> On Thu, Jun 1, 2023 at 11:24 AM Stamatis Zampetakis <za...@gmail.com>
>> wrote:
>>
>>> +1 from me as well. Any alpha or beta name should be fine I have no
>>> strong preferences.
>>>
>>> On Wed, May 31, 2023, 2:30 PM László Bodor <bo...@gmail.com>
>>> wrote:
>>>
>>> > Hi!
>>> >
>>> > +1 for creating a new release before GA in the presence of possible
>>> > correctness problems. I'm not 100% sure about alpha or beta, I'm fine
>>> with
>>> > alpha-3.
>>> >
>>> > Regards,
>>> > Laszlo Bodor
>>> >
>>> > Denys Kuzmenko <dk...@apache.org> ezt írta (időpont: 2023. máj.
>>> 31.,
>>> > Sze, 14:22):
>>> >
>>> > > Hi folks,
>>> > >
>>> > > The master branch has many new features, bug fixes, and performance
>>> > > improvements since alpha-2. However, we still have several
>>> correctness
>>> > bugs
>>> > > [HIVE-26654] and performance issues that should be eliminated before
>>> the
>>> > > GA.
>>> > >
>>> > > Could we consider doing a beta release to keep at least a 6-month
>>> release
>>> > > cadence and also show the community that 4.0.0 GA is the next stop?
>>> > >
>>> > > Thanks,
>>> > > Denys
>>> > >
>>> >
>>>
>>
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Attila Turoczy <at...@cloudera.com.INVALID>.
Ayush just told me, the mailing list does not support images. It is a very
sad world :-(
Previous meme:
https://imgflip.com/i/7nuzql
On Thu, Jun 1, 2023 at 11:46 AM Attila Turoczy <at...@cloudera.com>
wrote:
> OK. Then let's go with beta. Please start. (if not started already) a vote
> for a release.
>
> I think we should have a more frequent release cadence. The community
> needs it, we need this, also without frequent release nobody will believe
> this project is healthy. I know the first will be the hardest, but we need
> to fix those issues and release them. Even a monthly release could be
> possible for hive. We are capable to do this!
>
> [image: image.png]
>
> -Attila
>
> On Thu, Jun 1, 2023 at 11:24 AM Stamatis Zampetakis <za...@gmail.com>
> wrote:
>
>> +1 from me as well. Any alpha or beta name should be fine I have no
>> strong preferences.
>>
>> On Wed, May 31, 2023, 2:30 PM László Bodor <bo...@gmail.com>
>> wrote:
>>
>> > Hi!
>> >
>> > +1 for creating a new release before GA in the presence of possible
>> > correctness problems. I'm not 100% sure about alpha or beta, I'm fine
>> with
>> > alpha-3.
>> >
>> > Regards,
>> > Laszlo Bodor
>> >
>> > Denys Kuzmenko <dk...@apache.org> ezt írta (időpont: 2023. máj.
>> 31.,
>> > Sze, 14:22):
>> >
>> > > Hi folks,
>> > >
>> > > The master branch has many new features, bug fixes, and performance
>> > > improvements since alpha-2. However, we still have several correctness
>> > bugs
>> > > [HIVE-26654] and performance issues that should be eliminated before
>> the
>> > > GA.
>> > >
>> > > Could we consider doing a beta release to keep at least a 6-month
>> release
>> > > cadence and also show the community that 4.0.0 GA is the next stop?
>> > >
>> > > Thanks,
>> > > Denys
>> > >
>> >
>>
>
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Attila Turoczy <at...@cloudera.com.INVALID>.
OK. Then let's go with beta. Please start. (if not started already) a vote
for a release.
I think we should have a more frequent release cadence. The community needs
it, we need this, also without frequent release nobody will believe this
project is healthy. I know the first will be the hardest, but we need to
fix those issues and release them. Even a monthly release could be possible
for hive. We are capable to do this!
[image: image.png]
-Attila
On Thu, Jun 1, 2023 at 11:24 AM Stamatis Zampetakis <za...@gmail.com>
wrote:
> +1 from me as well. Any alpha or beta name should be fine I have no
> strong preferences.
>
> On Wed, May 31, 2023, 2:30 PM László Bodor <bo...@gmail.com>
> wrote:
>
> > Hi!
> >
> > +1 for creating a new release before GA in the presence of possible
> > correctness problems. I'm not 100% sure about alpha or beta, I'm fine
> with
> > alpha-3.
> >
> > Regards,
> > Laszlo Bodor
> >
> > Denys Kuzmenko <dk...@apache.org> ezt írta (időpont: 2023. máj. 31.,
> > Sze, 14:22):
> >
> > > Hi folks,
> > >
> > > The master branch has many new features, bug fixes, and performance
> > > improvements since alpha-2. However, we still have several correctness
> > bugs
> > > [HIVE-26654] and performance issues that should be eliminated before
> the
> > > GA.
> > >
> > > Could we consider doing a beta release to keep at least a 6-month
> release
> > > cadence and also show the community that 4.0.0 GA is the next stop?
> > >
> > > Thanks,
> > > Denys
> > >
> >
>
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
+1 from me as well. Any alpha or beta name should be fine I have no
strong preferences.
On Wed, May 31, 2023, 2:30 PM László Bodor <bo...@gmail.com>
wrote:
> Hi!
>
> +1 for creating a new release before GA in the presence of possible
> correctness problems. I'm not 100% sure about alpha or beta, I'm fine with
> alpha-3.
>
> Regards,
> Laszlo Bodor
>
> Denys Kuzmenko <dk...@apache.org> ezt írta (időpont: 2023. máj. 31.,
> Sze, 14:22):
>
> > Hi folks,
> >
> > The master branch has many new features, bug fixes, and performance
> > improvements since alpha-2. However, we still have several correctness
> bugs
> > [HIVE-26654] and performance issues that should be eliminated before the
> > GA.
> >
> > Could we consider doing a beta release to keep at least a 6-month release
> > cadence and also show the community that 4.0.0 GA is the next stop?
> >
> > Thanks,
> > Denys
> >
>
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by László Bodor <bo...@gmail.com>.
Hi!
+1 for creating a new release before GA in the presence of possible
correctness problems. I'm not 100% sure about alpha or beta, I'm fine with
alpha-3.
Regards,
Laszlo Bodor
Denys Kuzmenko <dk...@apache.org> ezt írta (időpont: 2023. máj. 31.,
Sze, 14:22):
> Hi folks,
>
> The master branch has many new features, bug fixes, and performance
> improvements since alpha-2. However, we still have several correctness bugs
> [HIVE-26654] and performance issues that should be eliminated before the
> GA.
>
> Could we consider doing a beta release to keep at least a 6-month release
> cadence and also show the community that 4.0.0 GA is the next stop?
>
> Thanks,
> Denys
>
Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Posted by Denys Kuzmenko <dk...@apache.org>.
Hi folks,
The master branch has many new features, bug fixes, and performance improvements since alpha-2. However, we still have several correctness bugs [HIVE-26654] and performance issues that should be eliminated before the GA.
Could we consider doing a beta release to keep at least a 6-month release cadence and also show the community that 4.0.0 GA is the next stop?
Thanks,
Denys
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
The umbrella ticket is HIVE-26654 [1]. I am currently looking into
HIVE-26968 and probably gonna merge this in the following days.
Help in reviewing or fixing the remaining tickets would be much appreciated.
Best,
Stamatis
[1] https://issues.apache.org/jira/browse/HIVE-26654
On Tue, May 16, 2023 at 11:52 AM Attila Turoczy
<at...@cloudera.com.invalid> wrote:
>
> +2. Who is working now on the TPCDS regression? Can I / We help him/ her?
>
> -Attila
>
>
> On Tue, May 16, 2023 at 11:04 AM Stamatis Zampetakis <za...@gmail.com>
> wrote:
>
> > I agree with Attila we should do our best to come out with the next GA
> > soon. In order to do that we should treat the TPCDS regressions that are
> > already reported. It doesn't make much sense to give out a GA that cannot
> > run the whole TPCDS suite without crashing or returning wrong results.
> >
> > If solving all the problems in a reasonable timeframe is not possible then
> > I would suggest to cut another alpha or beta release.
> >
> > Best,
> > Stamatis
> >
> > On Fri, May 12, 2023, 6:36 PM Attila Turoczy <aturoczy@cloudera.com.invalid
> > >
> > wrote:
> >
> > > Could we please give some attention to this topic? I strongly believe
> > that
> > > we should put in every effort to release Hive 4. The Hive community needs
> > > to demonstrate that we are active and accomplishing exciting
> > developments.
> > > It is quite disheartening to note that our last major GA release was a
> > > staggering 5 years ago on 18th May 2018! The significance of version 4.0
> > > cannot be overstated, and we should definitely prioritize its promotion.
> > >
> > > [image: image.png]
> > >
> > > -Attila
> > >
> > > On Tue, May 9, 2023 at 8:23 PM Kirti Ruge <ki...@gmail.com> wrote:
> > >
> > >> I see a few tickets like HIVE-26400 which is a major milestone, are
> > >> resolved .
> > >> Can we reevaluate priorities of other JIRAs so that It may give us
> > clarity
> > >> GO/NO-GO for 4.0.0 GA release and its timeline?
> > >>
> > >>
> > >>
> > >> Thanks,
> > >> Kirti
> > >>
> > >> On Sat, Mar 25, 2023 at 3:27 PM Stamatis Zampetakis <za...@gmail.com>
> > >> wrote:
> > >>
> > >> > Regarding correctness, I think it makes sense to change default values
> > >> and
> > >> > possibly add a warning note when there's a known risk of wrong
> > results.
> > >> > Needless to say that we should try to fix as many issues as possible;
> > we
> > >> > still need volunteers to review open PRS.
> > >> >
> > >> > Performances regressions are trickier but if we have the query plans
> > >> (CBO +
> > >> > full) along with logs (including task counters) for fast and slow
> > >> execution
> > >> > we may be able to understand what happens. Don't hesitate to create
> > Jira
> > >> > tickets with these information if available.
> > >> >
> > >> > Last regarding 4.0.0 blockers, I don't think we need a special label.
> > >> The
> > >> > built-in and widely used priority "blocker" seems enough to capture
> > the
> > >> > importance and urgency of a ticket.
> > >> > Since I am the release manager for the next release I will go over
> > >> tickets
> > >> > marked as blockers and reevaluate priorities if necessary.
> > >> >
> > >> > Best,
> > >> > Stamatis
> > >> >
> > >> > On Thu, Mar 23, 2023, 10:27 AM Denys Kuzmenko <dk...@apache.org>
> > >> > wrote:
> > >> >
> > >> > > Thanks, Sungwoo for running the TPC-DS benchmark. Do we know if the
> > >> same
> > >> > > level of performance degradation was present in 4.0.0-alpha1?
> > >> > >
> > >> > > All: please use the `hive-4.0.0-must` label in a ticket if you think
> > >> it's
> > >> > > a show-stopper for the release.
> > >> > >
> > >> >
> > >>
> > >
> >
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Attila Turoczy <at...@cloudera.com.INVALID>.
+2. Who is working now on the TPCDS regression? Can I / We help him/ her?
-Attila
On Tue, May 16, 2023 at 11:04 AM Stamatis Zampetakis <za...@gmail.com>
wrote:
> I agree with Attila we should do our best to come out with the next GA
> soon. In order to do that we should treat the TPCDS regressions that are
> already reported. It doesn't make much sense to give out a GA that cannot
> run the whole TPCDS suite without crashing or returning wrong results.
>
> If solving all the problems in a reasonable timeframe is not possible then
> I would suggest to cut another alpha or beta release.
>
> Best,
> Stamatis
>
> On Fri, May 12, 2023, 6:36 PM Attila Turoczy <aturoczy@cloudera.com.invalid
> >
> wrote:
>
> > Could we please give some attention to this topic? I strongly believe
> that
> > we should put in every effort to release Hive 4. The Hive community needs
> > to demonstrate that we are active and accomplishing exciting
> developments.
> > It is quite disheartening to note that our last major GA release was a
> > staggering 5 years ago on 18th May 2018! The significance of version 4.0
> > cannot be overstated, and we should definitely prioritize its promotion.
> >
> > [image: image.png]
> >
> > -Attila
> >
> > On Tue, May 9, 2023 at 8:23 PM Kirti Ruge <ki...@gmail.com> wrote:
> >
> >> I see a few tickets like HIVE-26400 which is a major milestone, are
> >> resolved .
> >> Can we reevaluate priorities of other JIRAs so that It may give us
> clarity
> >> GO/NO-GO for 4.0.0 GA release and its timeline?
> >>
> >>
> >>
> >> Thanks,
> >> Kirti
> >>
> >> On Sat, Mar 25, 2023 at 3:27 PM Stamatis Zampetakis <za...@gmail.com>
> >> wrote:
> >>
> >> > Regarding correctness, I think it makes sense to change default values
> >> and
> >> > possibly add a warning note when there's a known risk of wrong
> results.
> >> > Needless to say that we should try to fix as many issues as possible;
> we
> >> > still need volunteers to review open PRS.
> >> >
> >> > Performances regressions are trickier but if we have the query plans
> >> (CBO +
> >> > full) along with logs (including task counters) for fast and slow
> >> execution
> >> > we may be able to understand what happens. Don't hesitate to create
> Jira
> >> > tickets with these information if available.
> >> >
> >> > Last regarding 4.0.0 blockers, I don't think we need a special label.
> >> The
> >> > built-in and widely used priority "blocker" seems enough to capture
> the
> >> > importance and urgency of a ticket.
> >> > Since I am the release manager for the next release I will go over
> >> tickets
> >> > marked as blockers and reevaluate priorities if necessary.
> >> >
> >> > Best,
> >> > Stamatis
> >> >
> >> > On Thu, Mar 23, 2023, 10:27 AM Denys Kuzmenko <dk...@apache.org>
> >> > wrote:
> >> >
> >> > > Thanks, Sungwoo for running the TPC-DS benchmark. Do we know if the
> >> same
> >> > > level of performance degradation was present in 4.0.0-alpha1?
> >> > >
> >> > > All: please use the `hive-4.0.0-must` label in a ticket if you think
> >> it's
> >> > > a show-stopper for the release.
> >> > >
> >> >
> >>
> >
>
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
I agree with Attila we should do our best to come out with the next GA
soon. In order to do that we should treat the TPCDS regressions that are
already reported. It doesn't make much sense to give out a GA that cannot
run the whole TPCDS suite without crashing or returning wrong results.
If solving all the problems in a reasonable timeframe is not possible then
I would suggest to cut another alpha or beta release.
Best,
Stamatis
On Fri, May 12, 2023, 6:36 PM Attila Turoczy <at...@cloudera.com.invalid>
wrote:
> Could we please give some attention to this topic? I strongly believe that
> we should put in every effort to release Hive 4. The Hive community needs
> to demonstrate that we are active and accomplishing exciting developments.
> It is quite disheartening to note that our last major GA release was a
> staggering 5 years ago on 18th May 2018! The significance of version 4.0
> cannot be overstated, and we should definitely prioritize its promotion.
>
> [image: image.png]
>
> -Attila
>
> On Tue, May 9, 2023 at 8:23 PM Kirti Ruge <ki...@gmail.com> wrote:
>
>> I see a few tickets like HIVE-26400 which is a major milestone, are
>> resolved .
>> Can we reevaluate priorities of other JIRAs so that It may give us clarity
>> GO/NO-GO for 4.0.0 GA release and its timeline?
>>
>>
>>
>> Thanks,
>> Kirti
>>
>> On Sat, Mar 25, 2023 at 3:27 PM Stamatis Zampetakis <za...@gmail.com>
>> wrote:
>>
>> > Regarding correctness, I think it makes sense to change default values
>> and
>> > possibly add a warning note when there's a known risk of wrong results.
>> > Needless to say that we should try to fix as many issues as possible; we
>> > still need volunteers to review open PRS.
>> >
>> > Performances regressions are trickier but if we have the query plans
>> (CBO +
>> > full) along with logs (including task counters) for fast and slow
>> execution
>> > we may be able to understand what happens. Don't hesitate to create Jira
>> > tickets with these information if available.
>> >
>> > Last regarding 4.0.0 blockers, I don't think we need a special label.
>> The
>> > built-in and widely used priority "blocker" seems enough to capture the
>> > importance and urgency of a ticket.
>> > Since I am the release manager for the next release I will go over
>> tickets
>> > marked as blockers and reevaluate priorities if necessary.
>> >
>> > Best,
>> > Stamatis
>> >
>> > On Thu, Mar 23, 2023, 10:27 AM Denys Kuzmenko <dk...@apache.org>
>> > wrote:
>> >
>> > > Thanks, Sungwoo for running the TPC-DS benchmark. Do we know if the
>> same
>> > > level of performance degradation was present in 4.0.0-alpha1?
>> > >
>> > > All: please use the `hive-4.0.0-must` label in a ticket if you think
>> it's
>> > > a show-stopper for the release.
>> > >
>> >
>>
>
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Attila Turoczy <at...@cloudera.com.INVALID>.
Could we please give some attention to this topic? I strongly believe that
we should put in every effort to release Hive 4. The Hive community needs
to demonstrate that we are active and accomplishing exciting developments.
It is quite disheartening to note that our last major GA release was a
staggering 5 years ago on 18th May 2018! The significance of version 4.0
cannot be overstated, and we should definitely prioritize its promotion.
[image: image.png]
-Attila
On Tue, May 9, 2023 at 8:23 PM Kirti Ruge <ki...@gmail.com> wrote:
> I see a few tickets like HIVE-26400 which is a major milestone, are
> resolved .
> Can we reevaluate priorities of other JIRAs so that It may give us clarity
> GO/NO-GO for 4.0.0 GA release and its timeline?
>
>
>
> Thanks,
> Kirti
>
> On Sat, Mar 25, 2023 at 3:27 PM Stamatis Zampetakis <za...@gmail.com>
> wrote:
>
> > Regarding correctness, I think it makes sense to change default values
> and
> > possibly add a warning note when there's a known risk of wrong results.
> > Needless to say that we should try to fix as many issues as possible; we
> > still need volunteers to review open PRS.
> >
> > Performances regressions are trickier but if we have the query plans
> (CBO +
> > full) along with logs (including task counters) for fast and slow
> execution
> > we may be able to understand what happens. Don't hesitate to create Jira
> > tickets with these information if available.
> >
> > Last regarding 4.0.0 blockers, I don't think we need a special label. The
> > built-in and widely used priority "blocker" seems enough to capture the
> > importance and urgency of a ticket.
> > Since I am the release manager for the next release I will go over
> tickets
> > marked as blockers and reevaluate priorities if necessary.
> >
> > Best,
> > Stamatis
> >
> > On Thu, Mar 23, 2023, 10:27 AM Denys Kuzmenko <dk...@apache.org>
> > wrote:
> >
> > > Thanks, Sungwoo for running the TPC-DS benchmark. Do we know if the
> same
> > > level of performance degradation was present in 4.0.0-alpha1?
> > >
> > > All: please use the `hive-4.0.0-must` label in a ticket if you think
> it's
> > > a show-stopper for the release.
> > >
> >
>
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Kirti Ruge <ki...@gmail.com>.
I see a few tickets like HIVE-26400 which is a major milestone, are
resolved .
Can we reevaluate priorities of other JIRAs so that It may give us clarity
GO/NO-GO for 4.0.0 GA release and its timeline?
Thanks,
Kirti
On Sat, Mar 25, 2023 at 3:27 PM Stamatis Zampetakis <za...@gmail.com>
wrote:
> Regarding correctness, I think it makes sense to change default values and
> possibly add a warning note when there's a known risk of wrong results.
> Needless to say that we should try to fix as many issues as possible; we
> still need volunteers to review open PRS.
>
> Performances regressions are trickier but if we have the query plans (CBO +
> full) along with logs (including task counters) for fast and slow execution
> we may be able to understand what happens. Don't hesitate to create Jira
> tickets with these information if available.
>
> Last regarding 4.0.0 blockers, I don't think we need a special label. The
> built-in and widely used priority "blocker" seems enough to capture the
> importance and urgency of a ticket.
> Since I am the release manager for the next release I will go over tickets
> marked as blockers and reevaluate priorities if necessary.
>
> Best,
> Stamatis
>
> On Thu, Mar 23, 2023, 10:27 AM Denys Kuzmenko <dk...@apache.org>
> wrote:
>
> > Thanks, Sungwoo for running the TPC-DS benchmark. Do we know if the same
> > level of performance degradation was present in 4.0.0-alpha1?
> >
> > All: please use the `hive-4.0.0-must` label in a ticket if you think it's
> > a show-stopper for the release.
> >
>
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
Regarding correctness, I think it makes sense to change default values and
possibly add a warning note when there's a known risk of wrong results.
Needless to say that we should try to fix as many issues as possible; we
still need volunteers to review open PRS.
Performances regressions are trickier but if we have the query plans (CBO +
full) along with logs (including task counters) for fast and slow execution
we may be able to understand what happens. Don't hesitate to create Jira
tickets with these information if available.
Last regarding 4.0.0 blockers, I don't think we need a special label. The
built-in and widely used priority "blocker" seems enough to capture the
importance and urgency of a ticket.
Since I am the release manager for the next release I will go over tickets
marked as blockers and reevaluate priorities if necessary.
Best,
Stamatis
On Thu, Mar 23, 2023, 10:27 AM Denys Kuzmenko <dk...@apache.org> wrote:
> Thanks, Sungwoo for running the TPC-DS benchmark. Do we know if the same
> level of performance degradation was present in 4.0.0-alpha1?
>
> All: please use the `hive-4.0.0-must` label in a ticket if you think it's
> a show-stopper for the release.
>
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Denys Kuzmenko <dk...@apache.org>.
Thanks, Sungwoo for running the TPC-DS benchmark. Do we know if the same level of performance degradation was present in 4.0.0-alpha1?
All: please use the `hive-4.0.0-must` label in a ticket if you think it's a show-stopper for the release.
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Sungwoo Park <ct...@pl.postech.ac.kr>.
For correctness, we can merge a few pull requests and change the default values
of a few configuration parameters, so that we can get the correct results for
the TPC-DS benchmark.
Another issue is a performance regression when compared with Hive 3.1. I ran the
TPC-DS benchmark using a scale factor of 10TB. Our internal testing shows that
the current snapshot of Hive 4 is 1.5 times slower than Hive 3.1. Here is a
summary of our internal testing on a cluster with 13 nodes, each with 256GB
memory and 6 SSDs.
Systems compared:
1. Trino 417 (using Java 11)
2. Hive 3.1 (a fork maintained by us)
3. Hive 4.0.0-SNAPSHOT (as of February 2023)
Results:
1. Trino 417
total execution time = 9633 seconds, geometric mean = 28.19 seconds
query 21 returns wrong results.
query 23 returns wrong results.
query 72 fails (with query.max-memory = 1440GB)
2. Hive 3.1
total execution time = 9900 seconds, geometric mean = 31.67 seconds
All the 99 queries return correct results.
3. Hive 4.0.0-SNAPSHOT
total execution time = 10584 seconds, geometric mean = 43.72 seconds
All the 99 queries return correct results.
Around the summer 2020, Hive 4.0.0-SNAPSHOT was noticeably faster than Hive 3.1,
although a few queries returned wrong results.
Not sure about how to fix the performance regression. Git bisecting is not a
practical option because 1) until last year, building 4.0.0-SNAPSHOT was not
smooth because of Tez dependency; 2) loadig 10TB TPC-DS data for each commit is
too much an overhead.
I am thinking about comparing DAG plans from Hive 3.1 and 4.0.0-SNAPSHOT for
those queries that exhibit performance regression. If you have any suggestion,
please let me know.
--- Sungwoo
On Tue, 21 Mar 2023, Stamatis Zampetakis wrote:
> Many thanks for running tests with 4.0.0 Sungwoo; it is invaluable
> help for getting out a stable Hive 4.
>
> I will review https://issues.apache.org/jira/browse/HIVE-26968 in the
> coming weeks; I have assigned myself as reviewer in the PR.
>
> Can some other people (committers or not) help in reviewing the
> remaining TPC-DS blockers for which we have a PR?
>
> Reminder: Good non-binding reviews are important and much appreciated
> by the community. They are also among the important metrics for
> becoming a Hive committer/PMC [1].
>
> Best,
> Stamatis
>
> [1] https://cwiki.apache.org/confluence/display/Hive/BecomingACommitter
>
> On Tue, Mar 14, 2023 at 12:07?PM Sungwoo Park <ct...@pl.postech.ac.kr> wrote:
>>
>> Hello,
>>
>> I would like to expand the list of blockers with HIVE-27138 [1] which fixes NPE
>> on mapjoin_filter_on_outerjoin.q.
>>
>> Currently mapjoin_filter_on_outerjoin.q is tested with MapReduce execution
>> engine and shows no problem. However, it shows a few problems when tested with
>> Tez execution engine. HIVE-27138 is the first fix found after analyzing
>> mapjoin_filter_on_outerjoin.q, and Seonggon will create a couple more tickets
>> later.
>>
>> In the meanwhile, it would be great if someone could review pull requests for
>> subtasks in HIVE-26654. (I moved to HIVE-26654 three tickets that I previously
>> requested code review for.)
>>
>> Best,
>>
>> --- Sungwoo
>> [1] https://issues.apache.org/jira/browse/HIVE-27138
>>
>> On Fri, 10 Mar 2023, Stamatis Zampetakis wrote:
>>
>>> Hi Kirti,
>>>
>>> Thanks for bringing up this topic.
>>>
>>> The master branch already has many new features; we don't need to wait for
>>> more to cut a GA.
>>>
>>> The main criterion for going GA is stability thus I would consider
>>> regressions as the only blockers for the release.
>>>
>>> If I recall well the only regressions discovered so far are some problems
>>> with TPC-DS queries so basically HIVE-26654 [1].
>>>
>>> I will let others chime in to include more tickets if necessary.
>>>
>>> Best,
>>> Stamatis
>>>
>>> [1] https://issues.apache.org/jira/browse/HIVE-26654
>>>
>>>
>>> On Wed, Mar 8, 2023 at 10:02?AM Kirti Ruge <ki...@gmail.com> wrote:
>>>
>>>> Hello Hive Dev,
>>>>
>>>> It has been about 6 months since Hive-4.0-alpha-2 was released in Nov 2022.
>>>> Would it be a good time to discuss about HIVE-4.0 GA release to the
>>>> community ? Can we have discussion on the new features/jdk support versions
>>>> which we want to publish as part of 4.0 GA , timeframe of release.
>>>>
>>>>
>>>> Thanks,
>>>> Kirti
>>>
>
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
Many thanks for running tests with 4.0.0 Sungwoo; it is invaluable
help for getting out a stable Hive 4.
I will review https://issues.apache.org/jira/browse/HIVE-26968 in the
coming weeks; I have assigned myself as reviewer in the PR.
Can some other people (committers or not) help in reviewing the
remaining TPC-DS blockers for which we have a PR?
Reminder: Good non-binding reviews are important and much appreciated
by the community. They are also among the important metrics for
becoming a Hive committer/PMC [1].
Best,
Stamatis
[1] https://cwiki.apache.org/confluence/display/Hive/BecomingACommitter
On Tue, Mar 14, 2023 at 12:07 PM Sungwoo Park <ct...@pl.postech.ac.kr> wrote:
>
> Hello,
>
> I would like to expand the list of blockers with HIVE-27138 [1] which fixes NPE
> on mapjoin_filter_on_outerjoin.q.
>
> Currently mapjoin_filter_on_outerjoin.q is tested with MapReduce execution
> engine and shows no problem. However, it shows a few problems when tested with
> Tez execution engine. HIVE-27138 is the first fix found after analyzing
> mapjoin_filter_on_outerjoin.q, and Seonggon will create a couple more tickets
> later.
>
> In the meanwhile, it would be great if someone could review pull requests for
> subtasks in HIVE-26654. (I moved to HIVE-26654 three tickets that I previously
> requested code review for.)
>
> Best,
>
> --- Sungwoo
> [1] https://issues.apache.org/jira/browse/HIVE-27138
>
> On Fri, 10 Mar 2023, Stamatis Zampetakis wrote:
>
> > Hi Kirti,
> >
> > Thanks for bringing up this topic.
> >
> > The master branch already has many new features; we don't need to wait for
> > more to cut a GA.
> >
> > The main criterion for going GA is stability thus I would consider
> > regressions as the only blockers for the release.
> >
> > If I recall well the only regressions discovered so far are some problems
> > with TPC-DS queries so basically HIVE-26654 [1].
> >
> > I will let others chime in to include more tickets if necessary.
> >
> > Best,
> > Stamatis
> >
> > [1] https://issues.apache.org/jira/browse/HIVE-26654
> >
> >
> > On Wed, Mar 8, 2023 at 10:02?AM Kirti Ruge <ki...@gmail.com> wrote:
> >
> >> Hello Hive Dev,
> >>
> >> It has been about 6 months since Hive-4.0-alpha-2 was released in Nov 2022.
> >> Would it be a good time to discuss about HIVE-4.0 GA release to the
> >> community ? Can we have discussion on the new features/jdk support versions
> >> which we want to publish as part of 4.0 GA , timeframe of release.
> >>
> >>
> >> Thanks,
> >> Kirti
> >
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Sungwoo Park <ct...@pl.postech.ac.kr>.
Hello,
I would like to expand the list of blockers with HIVE-27138 [1] which fixes NPE
on mapjoin_filter_on_outerjoin.q.
Currently mapjoin_filter_on_outerjoin.q is tested with MapReduce execution
engine and shows no problem. However, it shows a few problems when tested with
Tez execution engine. HIVE-27138 is the first fix found after analyzing
mapjoin_filter_on_outerjoin.q, and Seonggon will create a couple more tickets
later.
In the meanwhile, it would be great if someone could review pull requests for
subtasks in HIVE-26654. (I moved to HIVE-26654 three tickets that I previously
requested code review for.)
Best,
--- Sungwoo
[1] https://issues.apache.org/jira/browse/HIVE-27138
On Fri, 10 Mar 2023, Stamatis Zampetakis wrote:
> Hi Kirti,
>
> Thanks for bringing up this topic.
>
> The master branch already has many new features; we don't need to wait for
> more to cut a GA.
>
> The main criterion for going GA is stability thus I would consider
> regressions as the only blockers for the release.
>
> If I recall well the only regressions discovered so far are some problems
> with TPC-DS queries so basically HIVE-26654 [1].
>
> I will let others chime in to include more tickets if necessary.
>
> Best,
> Stamatis
>
> [1] https://issues.apache.org/jira/browse/HIVE-26654
>
>
> On Wed, Mar 8, 2023 at 10:02?AM Kirti Ruge <ki...@gmail.com> wrote:
>
>> Hello Hive Dev,
>>
>> It has been about 6 months since Hive-4.0-alpha-2 was released in Nov 2022.
>> Would it be a good time to discuss about HIVE-4.0 GA release to the
>> community ? Can we have discussion on the new features/jdk support versions
>> which we want to publish as part of 4.0 GA , timeframe of release.
>>
>>
>> Thanks,
>> Kirti
>
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
Hi Kirti,
From the tickets you shared, the only one that I would consider a blocker
is HIVE-26220.
Assuming that we fix HIVE-26220 in the coming weeks can someone from
downstream projects test things out based on the nightly builds?
If nobody is willing to test the fix for HIVE-26220 then we could lower the
priority till there is actual interest.
Best,
Stamatis
On Sun, Mar 12, 2023 at 9:24 AM Kirti Ruge <ki...@gmail.com> wrote:
> Thanks Stamatis !!!
> I see below JIRAs marked with label hive-4.0.0-must <
> https://issues.apache.org/jira/issues/?jql=labels+%3D+hive-4.0.0-must>
> and in unresolved status.
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=564 <
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=564>
>
>
> Thanks,
> Kirti
>
> HIVE-26400 <https://issues.apache.org/jira/browse/HIVE-26400>
> Provide docker images for Hive - PR in review
> https://github.com/apache/hive/pull/3448 <
> https://github.com/apache/hive/pull/3448>
>
> HIVE-26537 <https://issues.apache.org/jira/browse/HIVE-26537>
> Deprecate older APIs in the HMS. - PR in review
> https://github.com/apache/hive/pull/3599
>
> HIVE-26220 <https://issues.apache.org/jira/browse/HIVE-26220>
> Shade & relocate dependencies in hive-exec to avoid conflicting with
> downstream projects
>
> HIVE-26644 <https://issues.apache.org/jira/browse/HIVE-26644>
> Introduce auto sizing in HMS - stale PR.
> https://github.com/apache/hive/pull/3683
>
>
>
> > On 10-Mar-2023, at 10:20 PM, Stamatis Zampetakis <za...@gmail.com>
> wrote:
> >
> > Hi Kirti,
> >
> > Thanks for bringing up this topic.
> >
> > The master branch already has many new features; we don't need to wait
> for
> > more to cut a GA.
> >
> > The main criterion for going GA is stability thus I would consider
> > regressions as the only blockers for the release.
> >
> > If I recall well the only regressions discovered so far are some problems
> > with TPC-DS queries so basically HIVE-26654 [1].
> >
> > I will let others chime in to include more tickets if necessary.
> >
> > Best,
> > Stamatis
> >
> > [1] https://issues.apache.org/jira/browse/HIVE-26654
> >
> >
> > On Wed, Mar 8, 2023 at 10:02 AM Kirti Ruge <ki...@gmail.com>
> wrote:
> >
> >> Hello Hive Dev,
> >>
> >> It has been about 6 months since Hive-4.0-alpha-2 was released in Nov
> 2022.
> >> Would it be a good time to discuss about HIVE-4.0 GA release to the
> >> community ? Can we have discussion on the new features/jdk support
> versions
> >> which we want to publish as part of 4.0 GA , timeframe of release.
> >>
> >>
> >> Thanks,
> >> Kirti
>
>
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Kirti Ruge <ki...@gmail.com>.
Thanks Stamatis !!!
I see below JIRAs marked with label hive-4.0.0-must <https://issues.apache.org/jira/issues/?jql=labels+%3D+hive-4.0.0-must> and in unresolved status.
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=564 <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=564>
Thanks,
Kirti
HIVE-26400 <https://issues.apache.org/jira/browse/HIVE-26400>
Provide docker images for Hive - PR in review
https://github.com/apache/hive/pull/3448 <https://github.com/apache/hive/pull/3448>
HIVE-26537 <https://issues.apache.org/jira/browse/HIVE-26537>
Deprecate older APIs in the HMS. - PR in review
https://github.com/apache/hive/pull/3599
HIVE-26220 <https://issues.apache.org/jira/browse/HIVE-26220>
Shade & relocate dependencies in hive-exec to avoid conflicting with downstream projects
HIVE-26644 <https://issues.apache.org/jira/browse/HIVE-26644>
Introduce auto sizing in HMS - stale PR.
https://github.com/apache/hive/pull/3683
> On 10-Mar-2023, at 10:20 PM, Stamatis Zampetakis <za...@gmail.com> wrote:
>
> Hi Kirti,
>
> Thanks for bringing up this topic.
>
> The master branch already has many new features; we don't need to wait for
> more to cut a GA.
>
> The main criterion for going GA is stability thus I would consider
> regressions as the only blockers for the release.
>
> If I recall well the only regressions discovered so far are some problems
> with TPC-DS queries so basically HIVE-26654 [1].
>
> I will let others chime in to include more tickets if necessary.
>
> Best,
> Stamatis
>
> [1] https://issues.apache.org/jira/browse/HIVE-26654
>
>
> On Wed, Mar 8, 2023 at 10:02 AM Kirti Ruge <ki...@gmail.com> wrote:
>
>> Hello Hive Dev,
>>
>> It has been about 6 months since Hive-4.0-alpha-2 was released in Nov 2022.
>> Would it be a good time to discuss about HIVE-4.0 GA release to the
>> community ? Can we have discussion on the new features/jdk support versions
>> which we want to publish as part of 4.0 GA , timeframe of release.
>>
>>
>> Thanks,
>> Kirti
Re: [DISCUSS] HIVE 4.0 GA Release Proposal
Posted by Stamatis Zampetakis <za...@gmail.com>.
Hi Kirti,
Thanks for bringing up this topic.
The master branch already has many new features; we don't need to wait for
more to cut a GA.
The main criterion for going GA is stability thus I would consider
regressions as the only blockers for the release.
If I recall well the only regressions discovered so far are some problems
with TPC-DS queries so basically HIVE-26654 [1].
I will let others chime in to include more tickets if necessary.
Best,
Stamatis
[1] https://issues.apache.org/jira/browse/HIVE-26654
On Wed, Mar 8, 2023 at 10:02 AM Kirti Ruge <ki...@gmail.com> wrote:
> Hello Hive Dev,
>
> It has been about 6 months since Hive-4.0-alpha-2 was released in Nov 2022.
> Would it be a good time to discuss about HIVE-4.0 GA release to the
> community ? Can we have discussion on the new features/jdk support versions
> which we want to publish as part of 4.0 GA , timeframe of release.
>
>
> Thanks,
> Kirti