Skip to content

AWS Glue Schema decoding #2081

Answered by mihaitodor
davido912 asked this question in Q&A
Aug 24, 2023 · 1 comments · 1 reply
Discussion options

You must be logged in to vote

I believe this will require an enhancement to the schema_registry_* processors, since it looks like AWS Glue Schema uses a different approach: https://lenses.io/blog/2023/04/aws_glue_schema_registry_that_binds_apache_kafka/

AWS Glue Schema Registry uses a payload approach to identify schemas, utilizing 18 bytes. The schema identification process begins with the first byte (Byte 0), which is a version number. The following Byte 1 denotes whether compression is being used or not, and Bytes 2-17 hold a 128-bit UUID, representing the schema version ID.

The deserialization process considers the first Byte value, and if it is set to 3, then the Glue-based serialization is used. Otherwise, a …

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@davido912
Comment options

Answer selected by davido912
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
enhancement needs investigation It looks as though have all the information needed but investigation is required
2 participants