Destination S3-V2: avro schema matches legacy CDK #51553
+65
−2
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
Client reported that
_airbyte_extracted_at
was missing logical typetimestamp-millis
. During investigation I realized that_airbyte_raw_id
was also missing logical typeuuid
.Fixed both issues and added tests confirming that avro schemas match legacy schemas.
Why
I'm hacking this in surgically for now. However, the correct fix is to introduce TimestampMillis and UUID as discrete extended types (assuming this gets approved).
Also
For reference, a legacy schema pulled from the logs of the escalating client's previous runs: