feat: add source/redis adapter (Redis Streams)#132
Merged
Conversation
Consumer-group Inlet over go-redis: XREADGROUP consume, XACK on ack, pending XCLAIM redelivery on nak, dead-letter stream routing on term. Honest capabilities by assertion: SharedDurable (the consumer group), Seekable (entry-ID XRANGE replay), LagReporter (XINFO GROUPS / XLEN). No partitions, so PartitionKey is empty and the Hopper shards by Key; no ConsumerGroups, no Transactional. Own module, GOWORK=off, wired into the source CI matrices. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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
1 participant
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.
What this change does
Adds
source/redis, a Redis Streams ingress adapter for thesourceseam (one of the four roadmap items from #131). It's a consumer-groupInletover go-redis:XREADGROUPto consume,XACKon ack, pending-entryXCLAIMredelivery on nak, and dead-letter-stream routing on term.Capabilities are advertised honestly by type assertion, never a lowest-common-denominator lie:
XRANGEreplay.XINFO GROUPS/XLEN.Redis Streams has no partitions, so
PartitionKeyis empty and theHoppershards byKey; it offers noConsumerGroups(in the Kafka sense) and noTransactional, so those interfaces are deliberately not implemented.Why
Redis Streams is a common, low-ceremony ingress that many teams already run, so it rounds out the native-adapter set alongside Kafka and JetStream without dragging a heavyweight broker in. It's its own module built
GOWORK=off(go-redis never enters the core graph) and is wired into thesource-destinationsmatrix and the testcontainers integration leg.Relates to: follows up the source Tier-1 PR (#131).
Checklist
git commit -s) per the DCOtype: subject)mage checkruns in CI across the workspace and the GOWORK=off source destinations