Thanks for clarifying this for me, Max and Bolke! At Infoworks, we are building a Data Warehouse solution for our customers. While researching various orchestration / ETL tools, I discovered Airflow and found it to be amongst the most flexible solutions out there. We want to provide a UI-based workflow tool for our users and I am planning on using Airflow for that. I could use Oozie et al. instead, but the rich and ever-growing connectors that Airflow provides (among other things) makes me want to go with Airflow. The only deterrent for me at this point is having to generate code.
I am not sure if this conversation is in the scope of this mailing list (or of interest to others), but I am curious to know what others think about this and if having an API to author flows is something that might be of interest to the Airflow community. It sure seems of use to us. Arpan Dhandhania e: [email protected] m: +91 782 939 5618 — Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. > On Jul 10, 2017, at 9:52 PM, Bolke de Bruin <[email protected]> wrote: > > Not really defining workflows, but I can imagine (and did implement once and > probably will do again) the possibility to “submit” a dag. > > Bolke > >> On 10 Jul 2017, at 18:18, Maxime Beauchemin <[email protected]> >> wrote: >> >> I'm pretty sure in is not in scope to define workflows from the API. The >> API will mostly be there as an abstraction to communicate with the database. >> >> Max >
