Just a few known issues in master:
https://issues.apache.org/jira/issues/?jql=labels%20%3D%20hive-4.1.0-must%20and%20resolution%20%3D%20Unresolved
To get a better view of things, we need to execute TPC-DS workload against
branch-4.0.1 and master.
Butao Zhang
Replied Message
| From | Zhihua Deng |
| Date | 8/1/2024 11:47 |
| To | |
| Subject | Re: [DISCUS] Plan the next Hive release |
Hi All,
Hive 4.0.1 Overview:
Now there are six Hive issues that tagged with hive-4.0.1-must left un-merged
to branch-4.0, most of them are resolved o
Hi All,
Hive 4.0.1 Overview:
Now there are six Hive issues that tagged with hive-4.0.1-must left un-merged
to branch-4.0, most of them are resolved on the master. Regarding to TEZ-4557,
a workaround in Hive is to add the missing jars to the hive.aux.jars.path,
which is acceptable, from my pers
Hi Stamatis,
`It's been already 4 months since the release of Hive 4.0.0`. That's true,
Zhihua can give a more detailed view of things, however, the main reason is
that it took a while to resolve the identified bugs.
ATM the only blocking item is TEZ-4557, which might not be available until
Se
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
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
&g
ieve? 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
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
&g
s 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
> 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
> un
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 pr
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 volun
release of HIVE 0.11.0
> >> >>>
> >> >>> Best Regards
> >> >>> Amir Sanjar
> >> >>>
> >> >>> System Management Architect
> >> >>> PowerLinux Open Source Hadoop development lead
> >> >>>
1.0
>> >>>
>> >>> Best Regards
>> >>> Amir Sanjar
>> >>>
>> >>> System Management Architect
>> >>> PowerLinux Open Source Hadoop development lead
>> >>> IBM Senior Software Engineer
>> >>
ct
> >>> PowerLinux Open Source Hadoop development lead
> >>> IBM Senior Software Engineer
> >>> Phone# 512-286-8393
> >>> Fax# 512-838-8858
> >>>
> >>>
> >&g
development lead
>>> IBM Senior Software Engineer
>>> Phone# 512-286-8393
>>> Fax# 512-838-8858
>>>
>>>
>>>
>>> [image: Inactive hide details for Ashutosh Chauhan ---03/22/2013 01:32:40
>>> PM---Hey all, Its not bee
uhan ---03/22/2013 01:32:40 PM---Hey all, Its not been long since we
> > released 0.10 but a lot has gone in since then.
> >
> > From: Ashutosh Chauhan
> > To: dev@hive.apache.org,
> > Date: 03/22/2013 01:32 PM
> > Subject: next hive release
> > -
since we released 0.10 but a]Ashutosh
> Chauhan ---03/22/2013 01:32:40 PM---Hey all, Its not been long since we
> released 0.10 but a lot has gone in since then.
>
> From: Ashutosh Chauhan
> To: dev@hive.apache.org,
> Date: 03/22/2013 01:32 PM
> Subject: next hive release
>
-838-8858
From: Ashutosh Chauhan
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 in. Also,
ptf
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
22 matches
Mail list logo
