+1
I often get requests for such a feature. Not in the Gen AI space specifically,
but for simply having more human control over pipeline execution, to get a
human review/approval before starting an important task.
There also have been prior discussions on Airflow’s GitHub:
https://github.com/ap
+1 I like the idea. I think this can expand Apache Airflow usage in
different areas. It can enable lots of different possibilities via
orchestrating the business workflows.
On Wed, 21 May 2025, 16:43 Jarek Potiuk, wrote:
> +1. Sounds pretty useful to have it in Airflow.
>
> On Wed, May 21, 2025
+1. Sounds pretty useful to have it in Airflow.
On Wed, May 21, 2025 at 4:24 PM Vincent Beck wrote:
> +1 as well. I can see this feature useful in many different cases (and not
> only AI/ML related in my opinion). Happy to read the AIP and give feedbacks
> :)
>
> On 2025/05/21 07:37:01 Tom Rutte
+1 as well. I can see this feature useful in many different cases (and not only
AI/ML related in my opinion). Happy to read the AIP and give feedbacks :)
On 2025/05/21 07:37:01 Tom Rutter wrote:
> +1 here!. As part of our Airflow deployment, we have built a layer on top
> to do review/approve and
+1 here!. As part of our Airflow deployment, we have built a layer on top
to do review/approve and branching. It would be great for more of this to
be standardised (and managed in the community by developers who are more
skilled than me!).
On Wed, 21 May 2025 at 09:12, Ankit Chaurasia wrote:
> +
I really like the idea and see it to be a window for some AI use cases to
be onboarded with
the orchestration capabilities of Airflow.
I also concur with what Jens mentioned, it should be an opt-in / opt-out
feature without
impacting how Airflow works with schedule today.
As I see it, it's a spec
+1 for this. From an ML/LLM-Ops standpoint, the introduction of a "human in
the loop" operator appears exceptionally valuable. I can envision this
operator being effectively integrated into ML pipelines, allowing for
dynamic adjustments to model training parameters based on user feedback
received d
I'm +0 for it, I like the broad strokes of the idea but actual experience
will very much depend on how we implement it.
I do very much agree for it to have api support and if it would be good if
we can design it with some thought to what future extensions might be
needed on this feature.
--
Regard
+1 for the opt-in feature. Can clearly see the need for this to exist. And
for both UI and APIs. +1 with Julian's idea of Dags waiting for input.
Thanks,
- Avi
On Wed, May 21, 2025 at 3:42 AM Kalyan Reddy wrote:
> I'm +1 on the idea. There should probably be notifications when approval
> is nee
I'm +1 on the idea. There should probably be notifications when approval is
needed to continue a task. Additionally, a dashboard would be helpful for
viewing the tasks awaiting my approval. It kind of makes me remember approval
gates on Azure DevOps pipelines. Even integrations to Slack/PagerDu
I like this idea. As Jens mentioned, this should be an opt-in feature, and
starting with providers seems reasonable. After that, we could probably get
feedback from users and see how we could improve UI/UX.
Best,
Wei
> On May 21, 2025, at 5:36 AM, Jens Scheffler
> wrote:
>
> Hi All,
>
> oh
Hi All,
oh I am a bit "envy" on receiving the email because I am thinking about
EXACTLY the same propsal but did not file an AIP to discuss about
this... as a matter of personal capacity and I wanted to finish off
existing obligations before dropping new ideas.
The very same idea for me was
I like the idea! We built something similar where a task would send an
email with a report attached (Excel, of course). The user had to either
approve the report or flag an issue. If they didn't respond in 2 hours, it
escalated to a backup, then to the department lead. If no one responded,
the DAG
While this is an understandable idea, I think it's wrong to involve humans
to take a part into Airflow workflow.
Run with parameters. Read the logs. Retry.
Blocking the whole pipeline could not be acceptable: humans are not stable
resource for input, they may be sick or on vacation and who will be
I like this idea. Three notes/comments that come to mind:
I think API interactions are going to be critical here. For example, I could
imagine someone wanting to post a message to slack with a button to resume the
DAG without having to go back to the Airflow UI
I see this as being useful for a lo
Hey everyone,
This is a small technical change, but conceptually it is significant and
therefore bringing it to the devlist.
As we have been having conversations with Airflow users, who are using
Airflow for Gen AI applications, there are a couple of features that have
been brought up as being de
16 matches
Mail list logo
