different flow,
> re-run
> >> > data mid run through a new set of processors, fork it on the fly, you
> >> know,
> >> > whatever I want anytime I want "
> >> >
> >> > NiFi: "Yeah, I can do that"
> >> >
> >> > Everyon
ew set of processors, fork it on the fly, you
>> know,
>> > whatever I want anytime I want "
>> >
>> > NiFi: "Yeah, I can do that"
>> >
>> > Everyone Else: ".... I'm sorry... what?"
>> >
>> > -Origin
currently do in Airflow
using NiFi, but for our Airflow use cases, things like task duration
are interesting metrics to monitor and I don't immediately know how we
would do this with NiFi. Plus the different user communities make two
separate tools no bad thing.
On Thu, 15 Aug 2019 at 21:00, Mike
yone Else: " I'm sorry... what?"
> >
> > -Original Message-
> > From: Mike Thomsen
> > Sent: Thursday, August 15, 2019 2:00 PM
> > To: dev@nifi.apache.org
> > Subject: [EXT] Airflow and NiFi
> >
> > Does anyone see any areas where the
it on the fly, you know,
> whatever I want anytime I want "
>
> NiFi: "Yeah, I can do that"
>
> Everyone Else: " I'm sorry... what?"
>
> -Original Message-
> From: Mike Thomsen
> Sent: Thursday, August 15, 2019 2:00 PM
> To: dev@
that"
Everyone Else: " I'm sorry... what?"
-Original Message-
From: Mike Thomsen
Sent: Thursday, August 15, 2019 2:00 PM
To: dev@nifi.apache.org
Subject: [EXT] Airflow and NiFi
Does anyone see any areas where the two can complement each other and where we
might
