FrankYang0529 opened a new pull request, #68782:
URL: https://github.com/apache/airflow/pull/68782
Adds `SqsSharedStreamProducer` and `SqsSharedStreamTrigger` to the Amazon
provider, backing the producer-side ack channel for shared-stream triggers
(#67523). Many event-driven triggers watching the same SQS queue can now share
a single consumer.
## How it works
- `SqsSharedStreamProducer` owns one SQS consumer for a shared-stream group:
`open_stream` receives messages without deleting them and yields `(body,
SqsBrokerPayload)`; deletion happens only in `advance`.
- A background task extends each outstanding message's visibility timeout
while it is being processed, so a slow subscriber does not cause SQS to
redeliver a message still in flight.
- On `advance`: `acked` and `rejected` messages are deleted (rejected is
dropped); `failed` (ack timeout / overflow) resets visibility to `0` for
immediate redelivery; a broadcast no subscriber was online for is left to lapse
and be redelivered when a subscriber returns.
- The advance lane is the FIFO `MessageGroupId` when present, falling back
to the receipt handle, so FIFO groups advance in order while standard queues
get maximum per-message parallelism.
<!-- 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.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
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
-->
related: #67523
---
##### 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".
-->
- [X] Yes — Claude Code (Opus 4.8)
<!--
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`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
