Skip to content

AIP-82: Add common messaging system providers #52712

Open

Description

@jason810496

Body

related: #49938

Why

Several users have pointed out that the Event-Driven Scheduling feature introduced in Airflow 3 currently supports only Amazon SQS.

So I add Kafka common message queue provider in #49938, but there are still quite a few common providers that should be useful for airflow users to implement Event-Driven workflows.

What

Here are some common messaging systems:

reference for implementation: https://github.com/apache/airflow/pull/49938/files

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Activity

  1. 400Ping commented on Jul 2, 2025

    @400Ping
    Member

    Hi, may I try the pubsub one?

  2. Jasperora commented on Jul 2, 2025

    @Jasperora
    Contributor

    Hi, I would like to try the Redis one. Thanks!

  3. prdai commented on Jul 2, 2025

    @prdai
    Contributor

    hi, could I implement the "Azure Message Bus" one? thanks :)

  4. 33 remaining items

  5. potiuk commented on Mar 2, 2026

    @potiuk
    Member

    @prdai We are unassigning you from this issue as part of our updated assignment policy.

    This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.

    We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.

  6. potiuk commented on Mar 2, 2026

    @potiuk
    Member

    @arnoldmr01 We are unassigning you from this issue as part of our updated assignment policy.

    This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.

    We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.

  7. potiuk commented on Mar 2, 2026

    @potiuk
    Member

    @Jasperora We are unassigning you from this issue as part of our updated assignment policy.

    This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.

    We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.

  8. potiuk commented on Mar 2, 2026

    @potiuk
    Member

    @SZL741023 We are unassigning you from this issue as part of our updated assignment policy.

    This is not meant to discourage your contribution — quite the opposite! You are still very welcome to work on this issue and submit a PR for it. Simply comment that you are working on it and open a PR when ready.

    We found that formal assignments were not working well, as they often prevented others from contributing when the assignee was not actively working on the issue.

  9. aaron-y-chen commented on Aug 5, 2026

    @aaron-y-chen
    Contributor

    I'm picking up the Kinesis work since I couldn't find an existing implementation PR.

    I plan to split it into two PRs, following the Azure Service Bus approach:

  10. jason810496 commented on Aug 5, 2026

    @jason810496
    MemberAuthor

    I'm picking up the Kinesis work since I couldn't find an existing implementation PR.

    Sure! Big thanks for following-up on this feature.

  11. aaron-y-chen commented on Sep 22, 2026

    @aaron-y-chen
    Contributor

    The common-messaging integration for Kinesis is in #73509.

    While working on it, I found bugs in the docstrings of all common messaging system providers. I opened a simple PR #73588 to fix them.

  12. kaxil commented on Oct 1, 2026

    @kaxil
    Member

    All the items tracked here are now closed or merged. Can this be closed, or is there remaining work it should track?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions