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
Yes, at the risk of adding nothing more than a "me too," I nevertheless
wish to add my thanks. Good job!
On 8/15/19 12:04 PM, Jeff wrote:
Apache NiFi Developers,
Apache NiFi can now be built with Java 11! Thanks to those that helped
with the review and committing of several PRs to get us to
This is awesome work that will be crucial for a large part of the community
moving forward Jeff. Thanks for taking the lead on this and slogging through a
lot of difficult challenges.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE
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
We use NiFi for all our ETL, and have done so very happily for several
years (including persuading partner organisations to adopt it); we
have recently started using Airflow for scheduling periodic machine
learning algorithm execution and retraining.
My £0.02 - we probably could do everything we
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
The easiest way to do something like that would be to derive a new Docker
image from our image. You can put whatever custom features you want from
new NARs, to templates, to a whole flow.xml.gz in there.
On Thu, Aug 15, 2019 at 7:32 AM Tomer Leibovich
wrote:
> Hi,
>
> I'm currently working on
Apache NiFi Developers,
Apache NiFi can now be built with Java 11! Thanks to those that helped
with the review and committing of several PRs to get us to this point.
For all contributions going forward, developers, reviewers, and committers
need to make sure that PRs are verified by building
Hi,
I'm currently working on building a CI/CD for NiFi in my workplace.
My goal is to provide the developers with a ready-to-work platform without
the need for manual changes (import templates, configure registry and add
plugins) from their side.
I hoped you can tell me if there is a way to
11 matches
Mail list logo
