Add Kinesis Data Streams trigger - #71135
Open
aaron-y-chen wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Those failures seem to be caused by the same issue: There is already a PR to fix it: #71118 |
10 tasks
aaron-y-chen
force-pushed
the
add-kinesis-trigger
branch
from
August 5, 2026 07:39
4e1733b to
d7e4df5
Compare
aaron-y-chen
marked this pull request as ready for review
August 5, 2026 09:18
Contributor
Author
|
Waiting for another PR #71145 to be merged. |
aaron-y-chen
force-pushed
the
add-kinesis-trigger
branch
from
August 5, 2026 14:50
d7e4df5 to
5589794
Compare
Contributor
Author
|
Okay, all CI failures have been fixed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
related: #52712
This is the first PR for Kinesis part of #52712, I will integrate the trigger with the common-messaging interface and add a system/e2e test in the next PR.
Summary
Add an asynchronous Kinesis Data Streams trigger for consuming records without occupying worker slots.
The trigger polls all shards, emits JSON-serializable record batches, handles iterator expiry, throttling, pagination, and in-run resharding, and checkpoints per-shard sequence numbers when an asset state store is available. New shards first discovered after a restart honor the configured initial position, so
LATESTmay skip records written during the downtime.This is the provider-side foundation for the common-messaging integration tracked in #52712.
Was generative AI tooling used to co-author this PR?
Generated-by: [GPT 5.6-sol] following the guidelines