fix(events): serialize connector payloads as JSON text - #2077
Open
gopikrishna000 wants to merge 1 commit into
Open
fix(events): serialize connector payloads as JSON text#2077gopikrishna000 wants to merge 1 commit into
gopikrishna000 wants to merge 1 commit into
Conversation
gopikrishna000
force-pushed
the
fix/connector-event-json-string-payloads
branch
from
August 7, 2026 12:14
93784e5 to
8250ca2
Compare
gopikrishna000
force-pushed
the
fix/connector-event-json-string-payloads
branch
from
August 7, 2026 18:14
8250ca2 to
a64ed78
Compare
AmitsinghTanwar007
approved these changes
Aug 8, 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
2 participants
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
request_dataandresponse_datavalues as JSON text before Kafka publication.Why
These payloads can contain any Serde JSON value, including objects, arrays, and scalar values. Emitting one JSON-text layer gives downstream consumers a consistent wire representation.
Rollout dependency
Deploy the backward-compatible Vector change before deploying this UCS change.
The Vector change accepts both the current structured payloads and the new JSON-text payloads, preventing merchant-facing Prism audit logs from being double encoded during a rolling deployment.
Validation
cargo fmt --all -- --checkcargo check -p ucs_common_utils