You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When consuming topics with schema registered in SR, it is useful to get schema_id used to deserialize message in msg headers, or make
it available as tuple (obj_dict, schema id) from return value of class AvroDeserializer(Deserializer) _ call _.
Schema_id may be useful to maintain ingestion table on database side automatically. Because now we have pain. It is ok, we have deserialized msg automatically for us. But how to maintain database side ingestion table without knowing explicit schema of consumed message?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
When consuming topics with schema registered in SR, it is useful to get schema_id used to deserialize message in msg headers, or make
it available as tuple (obj_dict, schema id) from return value of class AvroDeserializer(Deserializer) _ call _.
Schema_id may be useful to maintain ingestion table on database side automatically. Because now we have pain. It is ok, we have deserialized msg automatically for us. But how to maintain database side ingestion table without knowing explicit schema of consumed message?
Beta Was this translation helpful? Give feedback.
All reactions