+1 (binding) for dropping Hive support

Alexandre

Le mer. 13 nov. 2024 à 17:31, Rui Abreu <[email protected]> a écrit :
>
> I agree with keeping this open until the next release is close and
> drop it if there is no interest from the community in rewriting the
> code.
>
> Thank you @Richard Zowalla
>
> On Wed, 13 Nov 2024 at 07:26, Jonas Krauss <[email protected]> wrote:
> >
> > Hi Richard,
> >
> > thanks for being communicative about changes like this, I really appreciate 
> > it.
> >
> > For us, as we do not use Hive at all, dropping the support is not an issue 
> > and I would rather like dev resources invested elsewhere.
> >
> > Regards/Gruß
> >
> > Jonas
> >
> > Am Mi., 13. Nov. 2024 um 08:21 Uhr schrieb Richard Zowalla 
> > <[email protected]>:
> >>
> >> Hi all,
> >>
> >> As of now, Hive 3.x has reached end-of-life (see 
> >> https://hive.apache.org/general/downloads/ ), and we need to consider 
> >> upgrading to Hive 4.0.x. This upgrade would require us to replace 
> >> hive-hcatalog-streaming with hive-streaming.
> >>
> >> I reached out to one of the Hive developers regarding any available 
> >> documentation on this migration, but unfortunately, no such documentation 
> >> currently exists. At a first glance it seems, that we need some rewriting 
> >> of the related module in order to get it running. The original developers 
> >> are long gone.
> >>
> >> Since we cannot rely on EOL software from a security perspective (given 
> >> the implications by CRA, etc.), we need to consider how to handle that 
> >> situation.
> >>
> >> Do we have any Hive users willing to do the upgrade? Otherwise, given 
> >> these circumstances, I’d like to open up a discussion on potentially 
> >> dropping Hive support in the next Apache Storm release.
> >>
> >> Please let me know your thoughts or concerns.
> >>
> >> Gruß
> >>
> >> Richard
> >>
> >>
> >> P.S. I cross posted this discussion to user@ in order to get some traction 
> >> from our community. Maybe someone is willing to do the upgrade ;-) If so, 
> >> please subscribe to dev@ and reply there.

Reply via email to