feat: Metadata propagation in source, source transformer, mapper, sink #210
+1,645
−101
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.
Fixes: #205
Notes
Change in OnSuccess message metadata
With the introduction of a shared
UserMetadataclass, theuserMetadatamember inMessageclass for OnSuccess message has been changed from:to
This is done so that the users can utilize the same UserMetadata for onSuccess message without conversion.
Furthermore, the new UserMetadata has been implemented in its current form since it allows parity with other SDKs (inner data holds Map of Map, instead of Map of KeyValueGroup) and also prevents the extra step of converting proto KeyValueGroup object to local KeyValueGroup class object and back.
Format of userMetadata and systemMetadata
Both
UserMetadataandSystemMetadataclasses have inner data in the format: