-
Notifications
You must be signed in to change notification settings - Fork 17.9k
AIP-82: Add common messaging system providers #52712
Copy link
Copy link
Open
Labels
AIP-82External event driven scheduling in AirflowExternal event driven scheduling in Airflowgood first issuekind:featureFeature RequestsFeature Requestskind:metaHigh-level information important to the communityHigh-level information important to the communityprovider:amazonAWS/Amazon - related issuesAWS/Amazon - related issuesprovider:googleGoogle (including GCP) related issuesGoogle (including GCP) related issuesprovider:microsoft-azureAzure-related issuesAzure-related issuesprovider:redis
Description
Activity
Metadata
Metadata
Assignees
Labels
AIP-82External event driven scheduling in AirflowExternal event driven scheduling in Airflowgood first issuekind:featureFeature RequestsFeature Requestskind:metaHigh-level information important to the communityHigh-level information important to the communityprovider:amazonAWS/Amazon - related issuesAWS/Amazon - related issuesprovider:googleGoogle (including GCP) related issuesGoogle (including GCP) related issuesprovider:microsoft-azureAzure-related issuesAzure-related issuesprovider:redis
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:
MskHook#69000reference for implementation: https://github.com/apache/airflow/pull/49938/files
Committer