docs: document Redis JSON fallback and non-FastStream interop#2906
Merged
Conversation
Clarify that BinaryMessageFormatV1 falls back to raw JSON / plain bytes, so FastStream can interoperate with non-FastStream publishers and subscribers without the removed JSONMessageFormat. Fix stale references to JSONMessageFormat and the outdated "JSON is the default" migration note. Addresses #2899 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
powersemmi
approved these changes
Jun 6, 2026
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.
Description
Improves the Redis message-format documentation to explain how FastStream interoperates with non-FastStream publishers and subscribers, following the confusion raised in discussion #2899 after
JSONMessageFormat/RedisJSONMessageParserwas removed in0.7.0.What changed in
docs/docs/en/redis/message_format.md:BinaryMessageFormatV1.parsealready falls back to a legacy JSON envelope ({"data": ..., "headers": ...}) and then to raw bytes, so no dedicated JSON format is needed.dictwith no extra config.broker._connection(the nativeredis.asyncio.Redisclient), withpublish/rpush/xaddper destination type.MessageFormat.JSONMessageFormatreferences from the switching examples and added a warning note about its removal.0.7.xstate.Fixes # (discussion #2899)
Type of change
Checklist
just lintshows no errors)just test-coveragejust static-analysis