Hi all,
Late to the party, but as a vendor I favour option 2 and not to abandon support
for the Hadoop NARs. There is a very long tail of folks using NiFi on Hadoop
and I’d sooner give them the opportunity to keep using and upgrading NiFi while
they decide what to do with their existing data
o
> > their products will be a good option if possible.
> >
> > GC
> >
> > ________
> > From: Isha Lamboo
> > Sent: Monday, March 27, 2023 9:04 AM
> > To: dev@nifi.apache.org
> > Subject: RE: [discuss] NiFi suppor
a good option if possible.
>
> GC
>
>
> From: Isha Lamboo
> Sent: Monday, March 27, 2023 9:04 AM
> To: dev@nifi.apache.org
> Subject: RE: [discuss] NiFi support for Hadoop ecosystem components
>
> From the perspective of a NiFi administrator:
>
> Re
From: Isha Lamboo
Sent: Monday, March 27, 2023 9:04 AM
To: dev@nifi.apache.org
Subject: RE: [discuss] NiFi support for Hadoop ecosystem components
From the perspective of a NiFi administrator:
Removing the xxxHDFS processors anytime soon (2.0) would be a huge issue for
us. It shouldn't
andor Soma Abonyi
Verzonden: maandag 27 maart 2023 12:31
Aan: dev@nifi.apache.org
Onderwerp: Re: [discuss] NiFi support for Hadoop ecosystem components
Thank you for raising this topic, Joe!
While I understand the desire to remove Hadoop components, I have mixed
feelings about removing one of the
the issue without having separate HiveQL processors.
>
> GC
> ____
> From: Bryan Bende
> Sent: Friday, March 24, 2023 4:05 PM
> To: dev@nifi.apache.org
> Subject: Re: [discuss] NiFi support for Hadoop ecosystem components
>
> I lean tow
.
Jeremy Dyer
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Chakravarty, G
Sent: Friday, March 24, 2023 4:36:43 PM
To: dev@nifi.apache.org
Subject: Re: [discuss] NiFi support for Hadoop ecosystem components
I am wondering if the standard Nifi jdbc/odbc proc
James
Some are definitely less fun than others with Hive being the most notable.
I should rephrase my vendor thing on point one: It is as far as I know all
vendor supported Hadoop components. Whether NiFi is or not is a different
point.
Option 2 is the most realistic I suspect but still want
I'm a Hadoop and Nifi user without vendor support so unsurprisingly aren't
keen on #1, but then relying on community support and development is always
going to be a risk for us. If it came to it, we'd probably stop using Nifi
rather than pay a vendor which would be a real shame.
Are certain
:05 PM
To: dev@nifi.apache.org
Subject: Re: [discuss] NiFi support for Hadoop ecosystem components
I lean towards option 2 with the caveat that maybe we don't have to
retain every Hadoop related component when creating this separate set
of components. Mainly I'm thinking that Hive has been the most
I lean towards option 2 with the caveat that maybe we don't have to
retain every Hadoop related component when creating this separate set
of components. Mainly I'm thinking that Hive has been the most
problematic to maintain so maybe that is dropped all together. I think
it would be unfortunate to
As one of the small number of people that fight the battle, I like the
idea of Option 1 (full disclosure: I work for a vendor). From a
community standpoint (I'm on the PMC) I'm not strongly opposed to
Option 2 although I wouldn't want to be the one managing and releasing
the artifacts :) Having
Team,
For the full time NiFi has been in Apache we've built with support for
various Hadoop ecosystem components like HDFS, Hive, HBase, others,
and more recently formats/serialization modes like necessary for
Parquet, Orc, Iceberg, etc..
All of these things however present endless challenges
13 matches
Mail list logo
