Nifi is used for ETL and focus on transformations and data movement.
Airflow is good for orchestration. Both tools have scheduling in common.
Airflow is good at where the data is already available and you want to
control jobs.
If your focus is more like the data integertion, manipulation and
i blame spell check for ‘complimentary’
On Thu, Aug 15, 2019 at 4:11 PM Joe Witt wrote:
> Love it.
>
> Airflow I see as an orchestrator of making other systems do things. Nifi
> i see as very focused on acquiring, manipulating, and routing data between
> systems.
>
> In short, I believe theyre
Love it.
Airflow I see as an orchestrator of making other systems do things. Nifi i
see as very focused on acquiring, manipulating, and routing data between
systems.
In short, I believe theyre complimentary in a given architecture. Someone
always tries to use one to do both of the things but
Yeah, pretty much.
On Thu, Aug 15, 2019 at 4:02 PM Peter Wicks (pwicks)
wrote:
> User: "I want to change my production flow while it's running, you know,
> mid stream just route my content to a completely different flow, re-run
> data mid run through a new set of processors, fork it on the fly,
User: "I want to change my production flow while it's running, you know, mid
stream just route my content to a completely 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"
Everyone
