; > > > 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:
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
gt; >>
> >> 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
> >>
itely 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
>>
> 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
> underst
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
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;
+1. Thank you Ayush, for pushing things forward!
I would like to volunteer for the 4.0.1 release.
Thanks,
Zhihua
On 2024/04/09 22:30:55 Ayush Saxena wrote:
> Hi All,
> As we all know Hive-4.0 is released. I think we should try to maintain a
> regular cadence for the 4.x release line.
> So, I
Hi All,
As we all know Hive-4.0 is released. I think we should try to maintain a
regular cadence for the 4.x release line.
So, I propose having a 4.0.1 release in the next 3 months or so, with some
critical bug fixes and improvements on top of our last 4.0.0 release.
We would need someone to
@hive.apache.org,
Date: 03/22/2013 01:32 PM
Subject: next hive release
--
Hey all,
Its not been long since we released 0.10 but a lot has gone in since
then.
There are quite a few query plan optimizations which has gone in.
Also,
ptf-windowing work
in since then.
From: Ashutosh Chauhan hashut...@apache.org
To: dev@hive.apache.org,
Date: 03/22/2013 01:32 PM
Subject: next hive release
--
Hey all,
Its not been long since we released 0.10 but a lot has gone in since
then.
There are quite a few
Hey all,
Its not been long since we released 0.10 but a lot has gone in since then.
There are quite a few query plan optimizations which has gone in. Also,
ptf-windowing work is winding down and should be ready for merge in a week
or so. After the merge, I think it will be a good time to create a
-838-8858
From: Ashutosh Chauhan hashut...@apache.org
To: dev@hive.apache.org,
Date: 03/22/2013 01:32 PM
Subject:next hive release
Hey all,
Its not been long since we released 0.10 but a lot has gone in since then.
There are quite a few query plan optimizations which has gone
:40 PM---Hey all, Its not been long since we
released 0.10 but a lot has gone in since then.
From: Ashutosh Chauhan hashut...@apache.org
To: dev@hive.apache.org,
Date: 03/22/2013 01:32 PM
Subject: next hive release
--
Hey all,
Its not been long since we
@hive.apache.org,
Date: 03/22/2013 01:32 PM
Subject: next hive release
--
Hey all,
Its not been long since we released 0.10 but a lot has gone in since
then.
There are quite a few query plan optimizations which has gone in. Also,
ptf-windowing work
15 matches
Mail list logo
