kafka-mesh: Add second cluster batching test (blueberries → cluster2) #1032
+45
−0
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.
PR #1031 tests batched producing only to
apricots(cluster1). To demonstrate the mesh filter's key behavior—splitting batched ProduceRequests across upstream clusters—add testing for a second topic routed to cluster2.Changes
example.rst: Extended Step 8 withblueberriestopic example showing 20 batched messages to cluster2verify.sh: Added test sending 20 messages toblueberries, verifying all arrive at cluster2Matches coverage of upstream
test_producing_with_batched_recordswhich validates cross-cluster batching withapricots→ cluster1 andberries→ cluster2.Original prompt
This pull request was created from Copilot chat.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.