Hi Everyone,

@Lisoda ,

I have raised a PR in ranger to update the hive version from 3.1 to hive 4
and fix the HIVECONF issues.
PR: https://github.com/apache/ranger/pull/400

Please help with the reviews.

Thanks!
Simhadri G


On Tue, Oct 8, 2024 at 10:31 AM Sankar Hariappan
<sankar.hariap...@microsoft.com.invalid> wrote:

> I honour community’s decision to EOL Hive 3.x which is fair based on
> consensus from community.
>
> I would like to acknowledge the efforts put in by contributors like Aman
> to backport 100+ patches from master to branch-3 and reviews from Vihang,
> Peter, Ayush which brought us close to 3.2 release.
>
> Thanks to all who contributed to branch-3 and pls continue to contribute
> to the success of Hive 4.x!
>
>
>
> PS: Pls excuse me if I didn’t callout any other major contributors.
>
>
>
> Thanks,
>
> Sankar
>
> *From:* vihang karajgaonkar <vihan...@apache.org>
> *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 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 don’t end up in a similar
> situation with Hive 4 in the future.
>
>
>
> Regards,
>
> Vihang
>
>
>
> On Tue, Oct 8, 2024 at 2:17 AM Stamatis Zampetakis <zabe...@gmail.com>
> wrote:
>
> 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 3.x EOL for a short period
> of time (1-2 weeks) but this goes against the will of the community and the
> spirit of the vote.
>
> I understand that this outcome may be a bit disappointing for those people
> that invested quite some effort in a new 3.x release but the truth is that
> it is dragging the project behind.
>
> Let's all do our best to solve any potential adoption blockers for the
> Hive 4 release. To do this though we also need feedback from our users and
> help from the other open source communities. We can't solve problems that
> we don't know they exist and we can't guess what other projects need so
> please create tickets or even better submit PRs to fix those.
>
> Best,
> Stamatis
>
>
>
> On Mon, Oct 7, 2024, 5:35 PM lisoda <lis...@yeah.net> wrote:
>
> 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" <dkuzme...@apache.org> 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. 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 was 
> >resolved in a recent HIVE-4.0.1 release
>
> >
>
> >Regards,
>
> >Denys
>
>

Reply via email to