ar
> *Sent:* 08 October 2024 07:50
> *To:* dev@hive.apache.org
> *Subject:* Re: Re: Re:Re:Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
>
>
>
> Thanks everyone for freely expressing their opinions. Obviously it looks
> like some of the members here have strong opinions on wha
: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Thanks everyone for freely expressing their opinions. Obviously it looks like
some of the members here have strong opinions on what should be the future of
Hive 3.x and since the consensus is towards EOLing it, I am not going to pursue
this anymore.
Let’s move
Thanks everyone for freely expressing their opinions. Obviously it looks
like some of the members here have strong opinions on what should be the
future of Hive 3.x and since the consensus is towards EOLing it, I am not
going to pursue this anymore.
Let’s move forward with Hive 4 and make sure we
Declaring Hive 3 as EOL is the right thing to do and as far as I see
everyone is convinced about this thus I am not planning to change/retract
my vote in the respective thread.
Based on the current situation the 3.x EOL vote will pass. I was thinking
that we could postpone the announcement for the
The main problem is that HIVE4 changed the variable names in HIVECONF, which
caused some problems.
At 2024-10-07 23:32:46, "Denys Kuzmenko" wrote:
>Hi @lisoda
>
>Thanks for bringing up the Ranger issue. It would be very helpful if you could
>share the JIRA with the issue details. Down
Hi @lisoda
Thanks for bringing up the Ranger issue. It would be very helpful if you could
share the JIRA with the issue details. Downstream we are using a version
somewhat close to Hive-4.0 and it is fully integrated with Ranger.
Another integration issue that I am familiar is HIVE-28211, that
>
>> Is there an updated doc to follow for making a release since I have never
>> done it before.
>>
>> Thanks,
>> Aman.
>>
>> Get Outlook for Android
>>
>> From: vihang karajgaonkar
>> Sent: Saturday,
Sat, 5 Oct 2024 at 11:21, Aman Raj wrote:
>>
>> Sure I can take up the release manager role for 3.2.0. Thanks Vihang, Sankar
>> and Stamatis for supporting this.
>>
>> Is there an updated doc to follow for making a release since I have never
>> done it before.
utlook for Android
>
> From: vihang karajgaonkar
> Sent: Saturday, October 5, 2024 11:07:36 AM
> To: dev@hive.apache.org
> Subject: Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
>
> Thanks Stamatis!
>
> Is this wiki up to date?
> htt
ysg>
From: vihang karajgaonkar
Sent: Saturday, October 5, 2024 11:07:36 AM
To: dev@hive.apache.org
Subject: Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
Thanks Stamatis!
Is this wiki up to date?
https://cwiki.apache.org/confluence/display/Hive/HowToRelease#HowToRelease-HiveRelease
I wil
Thanks Stamatis!
Is this wiki up to date?
https://cwiki.apache.org/confluence/display/Hive/HowToRelease#HowToRelease-HiveRelease
I will wait for a day or two to see if Aman wants to take the lead here. If
not, I can volunteer to release 3.2.0.
Thanks,
Vihang
On Fri, Oct 4, 2024 at 3:28 PM Stama
Hey Vihang,
If someone volunteers to become the release manager and can prepare an RC
in the next 1-2 weeks then personally I have no problem testing and voting
for it.
Even though the EOL vote has started we can postpone the announcement if
there's an RC in progress.
Best,
Stamatis
On Thu, Oct
While I agree with the overall sentiment and reasoning that we can all
focus on Hive 4.x I would like to register my protest about this decision.
There are 411 commits in branch-3 which are not in branch-3.1 most of those
are bug fixes on 3.1.3. The work/effort to backport these is already been
don
Marking the 3.x release line EOL has no impact on existing users; they
are free to continue using it as they have for the past two years.
This decision is primarily about development focus—we’re officially
acknowledging that we won’t be dedicating efforts to 3.x anymore,
which has already been the
Hive 3.1 is certainly the most widely adopted release line, however, we do not
see any activity on this line, even in terms of providing security fixes and
CVE backports. Hive 3.1.3, the most recent release of the 3.x, was released on
2022-06-17.
We don't want to scatter our resources so we foc
stabilize, if 3.x goes EOL, it may push the users
out of Hive.
Thanks,
Sankar
From: Simhadri G
Sent: 28 September 2024 23:26
To: dev@hive.apache.org
Subject: [EXTERNAL] Re: [DISCUSS] Hive 3.x release
I agree with Ayush and Butao Zhang.
Hive 4 introduces numerous new features, critical bug and
; this can also help the Hive
> community grow in a positive way.
>
> I am +1 for marking 3.x EOL.
>
>
>
> Thanks,
> Butao Zhang
> Replied Message ----
> From Ayush Saxena
> Date 9/28/2024 14:56
> To
> Subject Re: [DISCUSS] Hive 3.x release
> If I re
ive community grow in a
positive way.
I am +1 for marking 3.x EOL.
Thanks,
Butao Zhang
Replied Message
| From | Ayush Saxena |
| Date | 9/28/2024 14:56 |
| To | |
| Subject | Re: [DISCUSS] Hive 3.x release |
If I recall correctly, we were planning to call for a vote to mark 3.
If I recall correctly, we were planning to call for a vote to mark 3.x
EOL after the 4.0.1 release. It seems no one is actively pursuing the
3.x release line. Placing the burden of backporting security fixes,
managing the release, running tests (perf/tpcds/bugs), and validating
the release candidat
Thanks for starting this thread.
Last I checked, Aman Raj was driving the backports for branch-3. The
tracking ticket for this effort was
https://issues.apache.org/jira/browse/HIVE-26751 However, I don't see
recent activity on that ticket so I am not sure if they are actively
working on this anymo
20 matches
Mail list logo
