I have left several comments :-). And on interactive dag runs even after the explanation of Vikram I still don't have a clue what we want to accomplish there :-P.
I would like to see a mantra or team for Airflow 3. That helps nudging people in the same direction. Suggestions in the comments. Bolke Sent from my iPhone > On 4 May 2024, at 01:14, Vikram Koka <vik...@astronomer.io.invalid> wrote: > > Good point Jed. > I responded back to your comment in the doc as well and very open to > changing the term in the doc. > > Used the term "interactive DAG run" as the ability to invoke or trigger a > DAG run through the API, with the expectation of getting back a result > immediately. An alternate term could be a "synchronous DAG run". > > Regardless, this is a significant change so a good term to indicate the > expansion from "batch runs only" is warranted. Very open to different terms > here. > >> On Fri, May 3, 2024 at 4:05 PM Jed Cunningham <jedcunning...@apache.org> >> wrote: >> >> Very exciting! Looks like we will have a busy period of time ahead of us. >> Overall I like the plan so far, especially using this year's Airflow Summit >> as an opportunity to announce and gather feedback, and the 2025 version to >> pitch upgrading. >> >> I left a comment in the doc, but we might want to iterate on the >> terminology we use for high priority or "synchronous" DAG runs to serve LLM >> responses - I find "interactive DAG runs" a bit confusing. >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
