Re: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Rajesh Balamohan]

Congratulations Simhadri. :)

~Rajesh.B

On Fri, Apr 19, 2024 at 2:02 AM Aman Sinha  wrote:

> Congrats Simhadri !
>
> On Thu, Apr 18, 2024 at 12:25 PM Naveen Gangam
>  wrote:
>
>> Congrats Simhadri. Looking forward to many more contributions in the
>> future.
>>
>> On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala
>>  wrote:
>>
>>> Congratulations Simhadri  well deserved
>>>
>>> On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:
>>>
 Congratulations

 Missatge de Alessandro Solimando  del
 dia dj., 18 d’abr. 2024 a les 17:40:

> Great news, Simhadri, very well deserved!
>
> On Thu, 18 Apr 2024 at 15:07, Simhadri G 
> wrote:
>
>> Thanks everyone!
>> I really appreciate it, it means a lot to me :)
>> The Apache Hive project and its community have truly inspired me .
>> I'm grateful for the chance to contribute to such a remarkable project.
>>
>> Thanks!
>> Simhadri Govindappa
>>
>> On Thu, Apr 18, 2024 at 6:18 PM Sankar Hariappan
>>  wrote:
>>
>>> Congrats Simhadri!
>>>
>>>
>>>
>>> -Sankar
>>>
>>>
>>>
>>> *From:* Butao Zhang 
>>> *Sent:* Thursday, April 18, 2024 5:39 PM
>>> *To:* u...@hive.apache.org; dev 
>>> *Subject:* [EXTERNAL] Re: [ANNOUNCE] New Committer: Simhadri
>>> Govindappa
>>>
>>>
>>>
>>> You don't often get email from butaozha...@163.com. Learn why this
>>> is important 
>>>
>>> Congratulations Simhadri !!!
>>>
>>>
>>>
>>> Thanks.
>>>
>>>
>>> --
>>>
>>> *发件人**:* user-return-28075-butaozhang1=163@hive.apache.org <
>>> user-return-28075-butaozhang1=163@hive.apache.org> 代表 Ayush
>>> Saxena 
>>> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
>>> *收件人**:* dev ; u...@hive.apache.org <
>>> u...@hive.apache.org>
>>> *主题**:* [ANNOUNCE] New Committer: Simhadri Govindappa
>>>
>>>
>>>
>>> Hi All,
>>>
>>> Apache Hive's Project Management Committee (PMC) has invited
>>> Simhadri Govindappa to become a committer, and we are pleased to 
>>> announce
>>> that he has accepted.
>>>
>>>
>>>
>>> Please join me in congratulating him, Congratulations Simhadri,
>>> Welcome aboard!!!
>>>
>>>
>>>
>>> -Ayush Saxena
>>>
>>> (On behalf of Apache Hive PMC)
>>>
>>

 --
 --
 Pau Tallada Crespí
 Departament de Serveis
 Port d'Informació Científica (PIC)
 Tel: +34 93 170 2729
 --

Re: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Aman Sinha]

Congrats Simhadri !

On Thu, Apr 18, 2024 at 12:25 PM Naveen Gangam 
wrote:

> Congrats Simhadri. Looking forward to many more contributions in the
> future.
>
> On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala
>  wrote:
>
>> Congratulations Simhadri  well deserved
>>
>> On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:
>>
>>> Congratulations
>>>
>>> Missatge de Alessandro Solimando  del
>>> dia dj., 18 d’abr. 2024 a les 17:40:
>>>
 Great news, Simhadri, very well deserved!

 On Thu, 18 Apr 2024 at 15:07, Simhadri G  wrote:

> Thanks everyone!
> I really appreciate it, it means a lot to me :)
> The Apache Hive project and its community have truly inspired me . I'm
> grateful for the chance to contribute to such a remarkable project.
>
> Thanks!
> Simhadri Govindappa
>
> On Thu, Apr 18, 2024 at 6:18 PM Sankar Hariappan
>  wrote:
>
>> Congrats Simhadri!
>>
>>
>>
>> -Sankar
>>
>>
>>
>> *From:* Butao Zhang 
>> *Sent:* Thursday, April 18, 2024 5:39 PM
>> *To:* u...@hive.apache.org; dev 
>> *Subject:* [EXTERNAL] Re: [ANNOUNCE] New Committer: Simhadri
>> Govindappa
>>
>>
>>
>> You don't often get email from butaozha...@163.com. Learn why this
>> is important 
>>
>> Congratulations Simhadri !!!
>>
>>
>>
>> Thanks.
>>
>>
>> --
>>
>> *发件人**:* user-return-28075-butaozhang1=163@hive.apache.org <
>> user-return-28075-butaozhang1=163@hive.apache.org> 代表 Ayush
>> Saxena 
>> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
>> *收件人**:* dev ; u...@hive.apache.org <
>> u...@hive.apache.org>
>> *主题**:* [ANNOUNCE] New Committer: Simhadri Govindappa
>>
>>
>>
>> Hi All,
>>
>> Apache Hive's Project Management Committee (PMC) has invited Simhadri
>> Govindappa to become a committer, and we are pleased to announce that he
>> has accepted.
>>
>>
>>
>> Please join me in congratulating him, Congratulations Simhadri,
>> Welcome aboard!!!
>>
>>
>>
>> -Ayush Saxena
>>
>> (On behalf of Apache Hive PMC)
>>
>
>>>
>>> --
>>> --
>>> Pau Tallada Crespí
>>> Departament de Serveis
>>> Port d'Informació Científica (PIC)
>>> Tel: +34 93 170 2729
>>> --
>>>
>>>

Re: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Naveen Gangam]

Congrats Simhadri. Looking forward to many more contributions in the future.

On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala
 wrote:

> Congratulations Simhadri  well deserved
>
> On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:
>
>> Congratulations
>>
>> Missatge de Alessandro Solimando  del
>> dia dj., 18 d’abr. 2024 a les 17:40:
>>
>>> Great news, Simhadri, very well deserved!
>>>
>>> On Thu, 18 Apr 2024 at 15:07, Simhadri G  wrote:
>>>
 Thanks everyone!
 I really appreciate it, it means a lot to me :)
 The Apache Hive project and its community have truly inspired me . I'm
 grateful for the chance to contribute to such a remarkable project.

 Thanks!
 Simhadri Govindappa

 On Thu, Apr 18, 2024 at 6:18 PM Sankar Hariappan
  wrote:

> Congrats Simhadri!
>
>
>
> -Sankar
>
>
>
> *From:* Butao Zhang 
> *Sent:* Thursday, April 18, 2024 5:39 PM
> *To:* u...@hive.apache.org; dev 
> *Subject:* [EXTERNAL] Re: [ANNOUNCE] New Committer: Simhadri
> Govindappa
>
>
>
> You don't often get email from butaozha...@163.com. Learn why this is
> important 
>
> Congratulations Simhadri !!!
>
>
>
> Thanks.
>
>
> --
>
> *发件人**:* user-return-28075-butaozhang1=163@hive.apache.org <
> user-return-28075-butaozhang1=163@hive.apache.org> 代表 Ayush
> Saxena 
> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
> *收件人**:* dev ; u...@hive.apache.org <
> u...@hive.apache.org>
> *主题**:* [ANNOUNCE] New Committer: Simhadri Govindappa
>
>
>
> Hi All,
>
> Apache Hive's Project Management Committee (PMC) has invited Simhadri
> Govindappa to become a committer, and we are pleased to announce that he
> has accepted.
>
>
>
> Please join me in congratulating him, Congratulations Simhadri,
> Welcome aboard!!!
>
>
>
> -Ayush Saxena
>
> (On behalf of Apache Hive PMC)
>

>>
>> --
>> --
>> Pau Tallada Crespí
>> Departament de Serveis
>> Port d'Informació Científica (PIC)
>> Tel: +34 93 170 2729
>> --
>>
>>

Re: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Sai Hemanth Gantasala]

Congratulations Simhadri  well deserved

On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:

> Congratulations
>
> Missatge de Alessandro Solimando  del dia
> dj., 18 d’abr. 2024 a les 17:40:
>
>> Great news, Simhadri, very well deserved!
>>
>> On Thu, 18 Apr 2024 at 15:07, Simhadri G  wrote:
>>
>>> Thanks everyone!
>>> I really appreciate it, it means a lot to me :)
>>> The Apache Hive project and its community have truly inspired me . I'm
>>> grateful for the chance to contribute to such a remarkable project.
>>>
>>> Thanks!
>>> Simhadri Govindappa
>>>
>>> On Thu, Apr 18, 2024 at 6:18 PM Sankar Hariappan
>>>  wrote:
>>>
 Congrats Simhadri!



 -Sankar



 *From:* Butao Zhang 
 *Sent:* Thursday, April 18, 2024 5:39 PM
 *To:* u...@hive.apache.org; dev 
 *Subject:* [EXTERNAL] Re: [ANNOUNCE] New Committer: Simhadri Govindappa



 You don't often get email from butaozha...@163.com. Learn why this is
 important 

 Congratulations Simhadri !!!



 Thanks.


 --

 *发件人**:* user-return-28075-butaozhang1=163@hive.apache.org <
 user-return-28075-butaozhang1=163@hive.apache.org> 代表 Ayush Saxena
 
 *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
 *收件人**:* dev ; u...@hive.apache.org <
 u...@hive.apache.org>
 *主题**:* [ANNOUNCE] New Committer: Simhadri Govindappa



 Hi All,

 Apache Hive's Project Management Committee (PMC) has invited Simhadri
 Govindappa to become a committer, and we are pleased to announce that he
 has accepted.



 Please join me in congratulating him, Congratulations Simhadri, Welcome
 aboard!!!



 -Ayush Saxena

 (On behalf of Apache Hive PMC)

>>>
>
> --
> --
> Pau Tallada Crespí
> Departament de Serveis
> Port d'Informació Científica (PIC)
> Tel: +34 93 170 2729
> --
>
>

Re: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Alessandro Solimando]

Great news, Simhadri, very well deserved!

On Thu, 18 Apr 2024 at 15:07, Simhadri G  wrote:

> Thanks everyone!
> I really appreciate it, it means a lot to me :)
> The Apache Hive project and its community have truly inspired me . I'm
> grateful for the chance to contribute to such a remarkable project.
>
> Thanks!
> Simhadri Govindappa
>
> On Thu, Apr 18, 2024 at 6:18 PM Sankar Hariappan
>  wrote:
>
>> Congrats Simhadri!
>>
>>
>>
>> -Sankar
>>
>>
>>
>> *From:* Butao Zhang 
>> *Sent:* Thursday, April 18, 2024 5:39 PM
>> *To:* u...@hive.apache.org; dev 
>> *Subject:* [EXTERNAL] Re: [ANNOUNCE] New Committer: Simhadri Govindappa
>>
>>
>>
>> You don't often get email from butaozha...@163.com. Learn why this is
>> important 
>>
>> Congratulations Simhadri !!!
>>
>>
>>
>> Thanks.
>>
>>
>> --
>>
>> *发件人**:* user-return-28075-butaozhang1=163@hive.apache.org <
>> user-return-28075-butaozhang1=163@hive.apache.org> 代表 Ayush Saxena <
>> ayush...@gmail.com>
>> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
>> *收件人**:* dev ; u...@hive.apache.org <
>> u...@hive.apache.org>
>> *主题**:* [ANNOUNCE] New Committer: Simhadri Govindappa
>>
>>
>>
>> Hi All,
>>
>> Apache Hive's Project Management Committee (PMC) has invited Simhadri
>> Govindappa to become a committer, and we are pleased to announce that he
>> has accepted.
>>
>>
>>
>> Please join me in congratulating him, Congratulations Simhadri, Welcome
>> aboard!!!
>>
>>
>>
>> -Ayush Saxena
>>
>> (On behalf of Apache Hive PMC)
>>
>

Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Krisztian Kasa]

Congratulations Simhadri!

Regards,
Krisztian

On Thu, Apr 18, 2024 at 3:25 PM kokila narayanan <
kokilanarayana...@gmail.com> wrote:

> Congratulations Simhadri 
>
> On Thu, 18 Apr, 2024, 17:22 Ayush Saxena,  wrote:
>
>> Hi All,
>> Apache Hive's Project Management Committee (PMC) has invited Simhadri
>> Govindappa to become a committer, and we are pleased to announce that he
>> has accepted.
>>
>> Please join me in congratulating him, Congratulations Simhadri, Welcome
>> aboard!!!
>>
>> -Ayush Saxena
>> (On behalf of Apache Hive PMC)
>>
>

Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[kokila narayanan]

Congratulations Simhadri 

On Thu, 18 Apr, 2024, 17:22 Ayush Saxena,  wrote:

> Hi All,
> Apache Hive's Project Management Committee (PMC) has invited Simhadri
> Govindappa to become a committer, and we are pleased to announce that he
> has accepted.
>
> Please join me in congratulating him, Congratulations Simhadri, Welcome
> aboard!!!
>
> -Ayush Saxena
> (On behalf of Apache Hive PMC)
>

Re: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Simhadri G]

Thanks everyone!
I really appreciate it, it means a lot to me :)
The Apache Hive project and its community have truly inspired me . I'm
grateful for the chance to contribute to such a remarkable project.

Thanks!
Simhadri Govindappa

On Thu, Apr 18, 2024 at 6:18 PM Sankar Hariappan
 wrote:

> Congrats Simhadri!
>
>
>
> -Sankar
>
>
>
> *From:* Butao Zhang 
> *Sent:* Thursday, April 18, 2024 5:39 PM
> *To:* u...@hive.apache.org; dev 
> *Subject:* [EXTERNAL] Re: [ANNOUNCE] New Committer: Simhadri Govindappa
>
>
>
> You don't often get email from butaozha...@163.com. Learn why this is
> important 
>
> Congratulations Simhadri !!!
>
>
>
> Thanks.
>
>
> --
>
> *发件人**:* user-return-28075-butaozhang1=163@hive.apache.org <
> user-return-28075-butaozhang1=163@hive.apache.org> 代表 Ayush Saxena <
> ayush...@gmail.com>
> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
> *收件人**:* dev ; u...@hive.apache.org <
> u...@hive.apache.org>
> *主题**:* [ANNOUNCE] New Committer: Simhadri Govindappa
>
>
>
> Hi All,
>
> Apache Hive's Project Management Committee (PMC) has invited Simhadri
> Govindappa to become a committer, and we are pleased to announce that he
> has accepted.
>
>
>
> Please join me in congratulating him, Congratulations Simhadri, Welcome
> aboard!!!
>
>
>
> -Ayush Saxena
>
> (On behalf of Apache Hive PMC)
>

RE: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Sankar Hariappan]

Congrats Simhadri!

-Sankar

From: Butao Zhang 
Sent: Thursday, April 18, 2024 5:39 PM
To: u...@hive.apache.org; dev 
Subject: [EXTERNAL] Re: [ANNOUNCE] New Committer: Simhadri Govindappa

You don't often get email from butaozha...@163.com. 
Learn why this is important
Congratulations Simhadri !!!

Thanks.


发件人: 
user-return-28075-butaozhang1=163@hive.apache.org
 
mailto:user-return-28075-butaozhang1=163@hive.apache.org>>
 代表 Ayush Saxena mailto:ayush...@gmail.com>>
发送时间: 星期四, 四月 18, 2024 7:50 下午
收件人: dev mailto:dev@hive.apache.org>>; 
u...@hive.apache.org 
mailto:u...@hive.apache.org>>
主题: [ANNOUNCE] New Committer: Simhadri Govindappa

Hi All,
Apache Hive's Project Management Committee (PMC) has invited Simhadri 
Govindappa to become a committer, and we are pleased to announce that he has 
accepted.

Please join me in congratulating him, Congratulations Simhadri, Welcome 
aboard!!!

-Ayush Saxena
(On behalf of Apache Hive PMC)

Re: [DISCUS] Plan the next Hive release

[Denys Kuzmenko]

The idea is to cherry-pick individual bug fixes/improvements that could be 
easily tested to avoid a complete release test cycle (TPC-DS performance suite, 
multi-db tests, etc)

On 2024/04/18 11:22:09 Stamatis Zampetakis wrote:
> There are also many projects that never create minor version releases;
> it's up to each project to decide what fits best on each occasion.
> 
> I am not against minor releases nor suggest that this should be the
> way to go for every release from now onwards. I am just saying that at
> this point in time I don't see a big benefit to release from side
> branches.
> 
> Again the motivation for releasing early and often from master is that
> it has less maintenance overhead for the community and the end-users
> can benefit from all improvements as soon as possible. Certainly if we
> introduce breaking changes and big risky features this approach cannot
> work.
> 
> Anyways, I am glad that we are having this discussion and it's also
> very positive that we are talking about a new release in less than a
> month since 4.0.0 came out. No matter if it is 4.0.1 or 4.1.0 I am
> fully onboard and happy to help as much as I can :)
> 
> Best,
> Stamatis
> 
> On Thu, Apr 18, 2024 at 11:53 AM Denys Kuzmenko  wrote:
> >
> > Hi Stamatis,
> >
> > That is the standard practice to create minor version release for bugfixes. 
> > Many upstream projects follow that same strategy, check Iceberg for example.
> >
> > Regards,
> > Denys
> >
> > On 2024/04/18 07:49:59 Stamatis Zampetakis wrote:
> > > The 4.0.0 release was quite recent so I assume we don't have major
> > > breaking changes in there at the moment so we could cut the release
> > > directly from master as soon as we want. HIVE-28166 is already merged
> > > so we could aim to cut 4.1.0 as soon as HIVE-28190 goes in.
> > >
> > > The experience shows that we are not very good at maintaining multiple
> > > release branches so in general I would prefer to focus on releasing
> > > only from master for the time being. Hive is a quite mature project so
> > > in principle breaking changes should be rather rare which gives us a
> > > bit of margin. I think a scheme where we backport less and release
> > > more is preferable.
> > >
> > > Best,
> > > Stamatis
> > >
> > > On Wed, Apr 17, 2024 at 9:56 AM Ayush Saxena  wrote:
> > > >
> > > > Hi Stamatis,
> > > > The plan is to have a release line cut from the branch-4.0, So, we plan 
> > > > to pull in some critical bug fixes & improvements into the 4.0.1 
> > > > release and have a quicker release.
> > > > As of now we are just putting the label "hive-4.0.1-must" on the 
> > > > tickets and we plan to make sure those get c-picked to the release 
> > > > line. AFAIK we haven't started committing to any branch yet, was 
> > > > waiting if anyone feels differently, so we can hold back if you have 
> > > > concerns or take a different approach as well.
> > > >
> > > > From CI you mean to say the daily builds? else if you create a PR 
> > > > targeting to branch-4.0, it will run the entire test suite I believe? 
> > > > In the meantime I will update the instructions regarding the target 
> > > > branch & the label if anyone wants that a particular ticket to be part 
> > > > of the 4.0.1 release.
> > > >
> > > > -Ayush
> > > >
> > > > On Wed, 17 Apr 2024 at 12:42, Stamatis Zampetakis  
> > > > wrote:
> > > >>
> > > >> Thanks for starting the discussion Ayush.
> > > >>
> > > >> Having frequent releases is definitely needed so we should keep the
> > > >> momentum going.
> > > >>
> > > >> I had the impression from other threads that the next Hive release
> > > >> would be 4.1.0 and that it would be cut from master. I would like to
> > > >> understand how 4.0.1 is different and if it is, what is the
> > > >> contribution pattern that contributors and committers should follow?
> > > >> If the idea is to maintain and commit in two (or more) branches the
> > > >> steps should be documented and CI should be running on those branches.
> > > >>
> > > >> Best,
> > > >> Stamatis
> > > >>
> > > >> On Wed, Apr 10, 2024 at 1:18 PM Denys Kuzmenko  
> > > >> wrote:
> > > >> >
> > > >> > We might need it sooner as identified some critical issues in the 
> > > >> > recent code:
> > > >> > 1. HIVE-28166: Truncate on Iceberg table disregards the branch name 
> > > >> > and operates on a main;
> > > >> > 2. HIVE-28190: Materialized view rebuild lock heart-beating is 
> > > >> > broken;
> > >
> 

Re: Issue with joda-time library bundled in hive-exec:4.0.0

[Cheng Pan]

Simhadri, thank you for sharing the information.

Thanks,
Cheng Pan

Re: [DISCUSS] End of life for Hive 1.x, 2.x, 3.x

[Cheng Pan]

Hi Chao,

The Spark community is starting to discuss the 4.0 release[1], can we make the 
Hive 2.3.10 release happen soon?

[1] https://lists.apache.org/thread/nxmvz2j7kp96otzlnl3kd277knlb6qgb

Thanks,
Cheng Pan

On 2024/01/17 17:50:37 Chao Sun wrote:
> Hi Ayush,
> 
> I'm working on the last few commits to backport to the branch.
> Hopefully within 1-2 months I can start the release process. Our goal
> is to upgrade Hive 2.x before the Spark 4.0 release coming up mid this
> year.
> 
> Chao
> 
> On Tue, Jan 16, 2024 at 10:17 PM Ayush Saxena  wrote:
> >
> > Thanx everyone for the feedback, I have started a formal thread to mark 1.x
> > EOL. We can have one last release for 2.x as Chao mentioned, with some
> > required changes + our CVE's & get the release line marked as EOL then.
> >
> > @Chao Sun  Do let us know if you have a proposed
> > timeline for that.
> >
> > -Ayush
> >
> > On Wed, 17 Jan 2024 at 08:23, vihang karajgaonkar 
> > wrote:
> >
> > > I was confused about the subject line since it says 3.x as well along with
> > > 1.x and 2.x. Does this discussion include all 1.x, 2.x and 3.x or just 1.x
> > > and 2.x?
> > >
> > > I think it makes sense to EOL 1.x. Looks like 2.x is still being 
> > > maintained
> > > by Chao and I think we were backporting PRs to the 3.x line pretty 
> > > recently
> > > so I believe we should wait out for a release on Hive 3.x.
> > >
> > > Thanks,
> > > Vihang
> > >
> > > On Tue, Jan 16, 2024 at 3:40 PM Attila Turoczy
> > >  wrote:
> > >
> > > > Dear PMC's,
> > > >
> > > > Do we have a verdict / decision about this?
> > > >
> > > > -Attila
> > > >
> > > > On Wed, Jan 10, 2024 at 5:45 PM Chao Sun  wrote:
> > > >
> > > > > On Hive 2.x, I'm still preparing for another release 2.3.10 (Hive 2.3
> > > > > branch is being actively maintained so far). Hopefully this will be
> > > > > the last release in the branch-2 line.
> > > > >
> > > > > +1 on making Hive 1 EOL for the time being.
> > > > >
> > > > > Chao
> > > > >
> > > > > On Wed, Jan 10, 2024 at 8:10 AM Sankar Hariappan
> > > > >  wrote:
> > > > > >
> > > > > > +1 for making both Hive 1&2 EOL
> > > > > >
> > > > > > -Sankar
> > > > > > -Original Message-
> > > > > > From: Attila Turoczy 
> > > > > > Sent: Wednesday, January 10, 2024 7:37 PM
> > > > > > To: dev@hive.apache.org
> > > > > > Subject: [EXTERNAL] Re: [DISCUSS] End of life for Hive 1.x, 2.x, 3.x
> > > > > >
> > > > > > [You don't often get email from aturo...@cloudera.com.invalid. Learn
> > > > > why this is important at https://aka.ms/LearnAboutSenderIdentification
> > > ]
> > > > > >
> > > > > > +1 for making it EOL for Hive 1 and Hive 2. I do not think these 2
> > > > > product
> > > > > > branches are relevant in 2023.
> > > > > >
> > > > > > -Attila
> > > > > >
> > > > > > On Wed, Jan 10, 2024 at 12:59 PM Denys Kuzmenko <
> > > dkuzme...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > +1 for marking Hive 1.x EOL
> > > > > > >
> > > > > > > Assuming no volunteers willing to take ownership of branch-2
> > > > > maintenance,
> > > > > > > +1 to declare it EOL as well.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Denys
> > > > > > >
> > > > >
> > > >
> > >
>  

Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Butao Zhang]

  
  
  

Congratulations Simhadri !!!
Thanks.
  

 发件人: user-return-28075-butaozhang1=163@hive.apache.org  代表 Ayush Saxena 发送时间: 星期四, 四月 18, 2024 7:50 下午收件人: dev ; u...@hive.apache.org 主题: [ANNOUNCE] New Committer: Simhadri Govindappa Hi All,Apache Hive's Project Management Committee (PMC) has invited Simhadri Govindappa to become a committer, and we are pleased to announce that he has accepted.Please join me in congratulating him, Congratulations Simhadri, Welcome aboard!!!-Ayush Saxena(On behalf of Apache Hive PMC)

[ANNOUNCE] New Committer: Simhadri Govindappa

[Ayush Saxena]

Hi All,
Apache Hive's Project Management Committee (PMC) has invited Simhadri
Govindappa to become a committer, and we are pleased to announce that he
has accepted.

Please join me in congratulating him, Congratulations Simhadri, Welcome
aboard!!!

-Ayush Saxena
(On behalf of Apache Hive PMC)

Re: [DISCUS] Plan the next Hive release

[Stamatis Zampetakis]

There are also many projects that never create minor version releases;
it's up to each project to decide what fits best on each occasion.

I am not against minor releases nor suggest that this should be the
way to go for every release from now onwards. I am just saying that at
this point in time I don't see a big benefit to release from side
branches.

Again the motivation for releasing early and often from master is that
it has less maintenance overhead for the community and the end-users
can benefit from all improvements as soon as possible. Certainly if we
introduce breaking changes and big risky features this approach cannot
work.

Anyways, I am glad that we are having this discussion and it's also
very positive that we are talking about a new release in less than a
month since 4.0.0 came out. No matter if it is 4.0.1 or 4.1.0 I am
fully onboard and happy to help as much as I can :)

Best,
Stamatis

On Thu, Apr 18, 2024 at 11:53 AM Denys Kuzmenko  wrote:
>
> Hi Stamatis,
>
> That is the standard practice to create minor version release for bugfixes. 
> Many upstream projects follow that same strategy, check Iceberg for example.
>
> Regards,
> Denys
>
> On 2024/04/18 07:49:59 Stamatis Zampetakis wrote:
> > The 4.0.0 release was quite recent so I assume we don't have major
> > breaking changes in there at the moment so we could cut the release
> > directly from master as soon as we want. HIVE-28166 is already merged
> > so we could aim to cut 4.1.0 as soon as HIVE-28190 goes in.
> >
> > The experience shows that we are not very good at maintaining multiple
> > release branches so in general I would prefer to focus on releasing
> > only from master for the time being. Hive is a quite mature project so
> > in principle breaking changes should be rather rare which gives us a
> > bit of margin. I think a scheme where we backport less and release
> > more is preferable.
> >
> > Best,
> > Stamatis
> >
> > On Wed, Apr 17, 2024 at 9:56 AM Ayush Saxena  wrote:
> > >
> > > Hi Stamatis,
> > > The plan is to have a release line cut from the branch-4.0, So, we plan 
> > > to pull in some critical bug fixes & improvements into the 4.0.1 release 
> > > and have a quicker release.
> > > As of now we are just putting the label "hive-4.0.1-must" on the tickets 
> > > and we plan to make sure those get c-picked to the release line. AFAIK we 
> > > haven't started committing to any branch yet, was waiting if anyone feels 
> > > differently, so we can hold back if you have concerns or take a different 
> > > approach as well.
> > >
> > > From CI you mean to say the daily builds? else if you create a PR 
> > > targeting to branch-4.0, it will run the entire test suite I believe? In 
> > > the meantime I will update the instructions regarding the target branch & 
> > > the label if anyone wants that a particular ticket to be part of the 
> > > 4.0.1 release.
> > >
> > > -Ayush
> > >
> > > On Wed, 17 Apr 2024 at 12:42, Stamatis Zampetakis  
> > > wrote:
> > >>
> > >> Thanks for starting the discussion Ayush.
> > >>
> > >> Having frequent releases is definitely needed so we should keep the
> > >> momentum going.
> > >>
> > >> I had the impression from other threads that the next Hive release
> > >> would be 4.1.0 and that it would be cut from master. I would like to
> > >> understand how 4.0.1 is different and if it is, what is the
> > >> contribution pattern that contributors and committers should follow?
> > >> If the idea is to maintain and commit in two (or more) branches the
> > >> steps should be documented and CI should be running on those branches.
> > >>
> > >> Best,
> > >> Stamatis
> > >>
> > >> On Wed, Apr 10, 2024 at 1:18 PM Denys Kuzmenko  
> > >> wrote:
> > >> >
> > >> > We might need it sooner as identified some critical issues in the 
> > >> > recent code:
> > >> > 1. HIVE-28166: Truncate on Iceberg table disregards the branch name 
> > >> > and operates on a main;
> > >> > 2. HIVE-28190: Materialized view rebuild lock heart-beating is broken;
> >

Re: [Blog] Apache Hive 4.0 Release blog for ASF M & P

[Ayush Saxena]

Update:
I submitted this last week, and I circled back to check, this is being
reviewed and they are dropping, tweaking a couple of things and writing
some Apache stuff & all to follow their template(Which I should have done
myself, they shared the template of Apache Wicket), those things we don’t
have any control over. M folks will take care of it. So, it will look a
bit different then what we submitted.

I have been communicated that:* It is supposed to be published before end
of month*

PS. They asked for some quotes for the release, which I have said I don’t
have. We can drop adding that, either they will drop or add from their own.
But I think they will write something themselves

I think it will be finalized soon, I will keep the thread updated as I get
anything or If I find it got published itself :-)

-Ayush


On 5 Apr 2024, at 5:39 PM, Ayush Saxena  wrote:


Hi Stamatis,
I have changed the permissions to allow everyone with the link to have
comment access. I have additionally given you edit access as well.

Let me know if things don't work

-Ayush

On Fri, 5 Apr 2024 at 17:34, Stamatis Zampetakis  wrote:

> Great initiative and nice content. Overall, it looks great!
>
> I have some minor comments. Is it possible to change permissions allow
> comments from anyone or it has to be done on a per user basis?
>
> Best,
> Stamatis
>
> On Fri, Apr 5, 2024 at 1:54 PM Ayush Saxena  wrote:
> >
> > Hi All,
> >
> > Have been talking to the ASF M & P team and they recongonise the 4.0
> release is a big milestone for our project.
> >
> > They are happy to have an entry for us in the their news column, ex:
> >
> https://news.apache.org/foundation/entry/apache-software-foundation-announces-apache-wicket-v10
> >
> > So, I along with Denys, Simhadri & tons of help from ChatGpt have
> prepared a draft to share with them.
> > The draft is here:
> >
> >
> https://docs.google.com/document/d/10Zu8pHvWNDRTqn7yvYqvU4-kw3Q1TXo7mGo5m5fUP2Y/edit
> >
> > If you have some feedback or concerns, please share with us.
> >
> > If you want some improvements or removals, let us know here & we will do
> that, or if you need write access to this page, just let me know.
> >
> > If nobody objects, I plan to send this to the team by next week Tuesday
> >
> >
> > -Ayush
>

Re: [DISCUS] Plan the next Hive release

[Denys Kuzmenko]

Hi Stamatis,

That is the standard practice to create minor version release for bugfixes. 
Many upstream projects follow that same strategy, check Iceberg for example.

Regards,
Denys

On 2024/04/18 07:49:59 Stamatis Zampetakis wrote:
> The 4.0.0 release was quite recent so I assume we don't have major
> breaking changes in there at the moment so we could cut the release
> directly from master as soon as we want. HIVE-28166 is already merged
> so we could aim to cut 4.1.0 as soon as HIVE-28190 goes in.
> 
> The experience shows that we are not very good at maintaining multiple
> release branches so in general I would prefer to focus on releasing
> only from master for the time being. Hive is a quite mature project so
> in principle breaking changes should be rather rare which gives us a
> bit of margin. I think a scheme where we backport less and release
> more is preferable.
> 
> Best,
> Stamatis
> 
> On Wed, Apr 17, 2024 at 9:56 AM Ayush Saxena  wrote:
> >
> > Hi Stamatis,
> > The plan is to have a release line cut from the branch-4.0, So, we plan to 
> > pull in some critical bug fixes & improvements into the 4.0.1 release and 
> > have a quicker release.
> > As of now we are just putting the label "hive-4.0.1-must" on the tickets 
> > and we plan to make sure those get c-picked to the release line. AFAIK we 
> > haven't started committing to any branch yet, was waiting if anyone feels 
> > differently, so we can hold back if you have concerns or take a different 
> > approach as well.
> >
> > From CI you mean to say the daily builds? else if you create a PR targeting 
> > to branch-4.0, it will run the entire test suite I believe? In the meantime 
> > I will update the instructions regarding the target branch & the label if 
> > anyone wants that a particular ticket to be part of the 4.0.1 release.
> >
> > -Ayush
> >
> > On Wed, 17 Apr 2024 at 12:42, Stamatis Zampetakis  wrote:
> >>
> >> Thanks for starting the discussion Ayush.
> >>
> >> Having frequent releases is definitely needed so we should keep the
> >> momentum going.
> >>
> >> I had the impression from other threads that the next Hive release
> >> would be 4.1.0 and that it would be cut from master. I would like to
> >> understand how 4.0.1 is different and if it is, what is the
> >> contribution pattern that contributors and committers should follow?
> >> If the idea is to maintain and commit in two (or more) branches the
> >> steps should be documented and CI should be running on those branches.
> >>
> >> Best,
> >> Stamatis
> >>
> >> On Wed, Apr 10, 2024 at 1:18 PM Denys Kuzmenko  
> >> wrote:
> >> >
> >> > We might need it sooner as identified some critical issues in the recent 
> >> > code:
> >> > 1. HIVE-28166: Truncate on Iceberg table disregards the branch name and 
> >> > operates on a main;
> >> > 2. HIVE-28190: Materialized view rebuild lock heart-beating is broken;
> 

Re: [DISCUS] Plan the next Hive release

[Stamatis Zampetakis]

The 4.0.0 release was quite recent so I assume we don't have major
breaking changes in there at the moment so we could cut the release
directly from master as soon as we want. HIVE-28166 is already merged
so we could aim to cut 4.1.0 as soon as HIVE-28190 goes in.

The experience shows that we are not very good at maintaining multiple
release branches so in general I would prefer to focus on releasing
only from master for the time being. Hive is a quite mature project so
in principle breaking changes should be rather rare which gives us a
bit of margin. I think a scheme where we backport less and release
more is preferable.

Best,
Stamatis

On Wed, Apr 17, 2024 at 9:56 AM Ayush Saxena  wrote:
>
> Hi Stamatis,
> The plan is to have a release line cut from the branch-4.0, So, we plan to 
> pull in some critical bug fixes & improvements into the 4.0.1 release and 
> have a quicker release.
> As of now we are just putting the label "hive-4.0.1-must" on the tickets and 
> we plan to make sure those get c-picked to the release line. AFAIK we haven't 
> started committing to any branch yet, was waiting if anyone feels 
> differently, so we can hold back if you have concerns or take a different 
> approach as well.
>
> From CI you mean to say the daily builds? else if you create a PR targeting 
> to branch-4.0, it will run the entire test suite I believe? In the meantime I 
> will update the instructions regarding the target branch & the label if 
> anyone wants that a particular ticket to be part of the 4.0.1 release.
>
> -Ayush
>
> On Wed, 17 Apr 2024 at 12:42, Stamatis Zampetakis  wrote:
>>
>> Thanks for starting the discussion Ayush.
>>
>> Having frequent releases is definitely needed so we should keep the
>> momentum going.
>>
>> I had the impression from other threads that the next Hive release
>> would be 4.1.0 and that it would be cut from master. I would like to
>> understand how 4.0.1 is different and if it is, what is the
>> contribution pattern that contributors and committers should follow?
>> If the idea is to maintain and commit in two (or more) branches the
>> steps should be documented and CI should be running on those branches.
>>
>> Best,
>> Stamatis
>>
>> On Wed, Apr 10, 2024 at 1:18 PM Denys Kuzmenko  wrote:
>> >
>> > We might need it sooner as identified some critical issues in the recent 
>> > code:
>> > 1. HIVE-28166: Truncate on Iceberg table disregards the branch name and 
>> > operates on a main;
>> > 2. HIVE-28190: Materialized view rebuild lock heart-beating is broken;

Re: Issue with joda-time library bundled in hive-exec:4.0.0

[Simhadri G]

Hi Cheng Pan,

There is long running Hive mail thread discussing this here:
https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s


On Thu, Apr 18, 2024 at 11:15 AM Cheng Pan  wrote:

> Hi Ayush,
>
> > Hive is already in discussion of marking Hive-2.x EOL, so at very best
> we would have one release and immediately after that we will announce it EOL
>
> Does the discussion happen in public? Is there an ETA for the final
> release of branch-2.3?
>
> Thanks,
> Cheng Pan
>
>
> > On Apr 17, 2024, at 18:03, Ayush Saxena  wrote:
> >
> > Thanx Cheng Pan for sharing the pointers, Do you have any list of issues
> or pointers on what are the challenges for Spark to move to a higher Hive
> version? I know upgrading libraries is quite challenging but it is
> inevitable.
> >
> > Hive is already in discussion of marking Hive-2.x EOL, so at very best
> we would have one release and immediately after that we will announce it
> EOL, maintaining a release line is quite an effort for us at Hive & doing
> it because other projects doesn't want to upgrade isn't a convincing reason
> for most of us. The best we can do is or are trying is to address issues
> for Spark whatever we can do as part of Hive code & would definitely need
> help/support from Spark side as well, since the move is from 2.x to 4.x, it
> would be a big change and would offer resistance on both sides.
> >
> > So, it would be great help if any pointers can be shared from Spark side
> for the move, if there is no help/interest from Spark then we can't do
> anything & there is no need for Hive-2.x either in that case :-)
> >
> > -Ayush
> >
> > On Wed, 17 Apr 2024 at 15:00, Cheng Pan  wrote:
> > > … we are exploring ways to get Spark move from 2.3.9 to 4.0, Our
> initial hunch is that it would be quite challenging without a hive-exec
> slim jar …
> >
> > It should be challenging to upgrade Spark’s built-in Hive version.
> Actually, we already did lots of work on branch-2.3 which focuses on CVE
> reduction, for example, allowing Spark to upgrade Guava to modern versions
> to get rid of Guava 14, it was tested with the latest Spark master
> branch[1], maybe we need a release for 2.3.10 now.
> >
> > [1] https://github.com/apache/spark/pull/45372
> >
> > Thanks,
> > Cheng Pan
> >
> >
>
>