dabla opened a new pull request, #62790:
URL: https://github.com/apache/airflow/pull/62790
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
With the introduction of event-driven scheduling and the
MessageQueueProvider abstraction in Airflow, it has become significantly easier
to trigger DAGs from external message brokers as described in Astronomer's
guide on [event-driven
scheduling](https://www.astronomer.io/docs/learn/airflow-event-driven-scheduling).
Many enterprises still rely heavily on [IBM
MQ](https://www.ibm.com/products/mq) as their primary enterprise messaging
backbone. However, at the moment there is no official Airflow provider
supporting [IBM MQ](https://www.ibm.com/products/mq).
This implementation consists of:
* An IBMMQHook
* A MessageQueueProvider implementation for IBM MQ
* The ability to trigger DAGs from IBM MQ events
* Standard producer/consumer patterns from within tasks
This allows IBM MQ to function similarly to Kafka, SQS, etc., within the
Airflow event-driven scheduling framework.
The implementation is built on top of the open-source IBM MQ Python wrapper:
* IBM MQ Python [ibmmq](https://github.com/ibm-messaging/mq-mqi-python)
library
IBM has recently released and documented their modern Python binding here:
https://community.ibm.com/community/user/blogs/dylan-goode/2025/10/16/new-python-binding-for-ibm-mq
The hook supports:
* Secure connections (TLS) (to be done)
* Queue get/put operations
* Configurable polling behaviour
The MessageQueueProvider implementation integrates with Airflow's
event-driven scheduling so that DAGs can be triggered based on IBM MQ messages.
Why this might make sense:
* IBM MQ is still widely used in regulated industries (banking, insurance,
government).
* Many enterprises using Airflow also run IBM MQ.
* This would allow IBM MQ to be a first-class citizen in Airflow's
event-driven ecosystem.
* The dependency is officially maintained by IBM and open source.
I am willing to act as initial maintainer and code owner, of course this is
purely a proposition.
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
