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
Have some questions on how consumer uses avro schema. Basic workflow is producer includes the id in message and consumer uses that id to get the schema from registry. My question is on schema evolving issue.
Since consumer uses the id to get the schema and for every evolved schema, a new id is generated on producer’s side, why are there compatibility issues on consumer’s side if consumer can always get the updated schema based on the new id from 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
-
Have some questions on how consumer uses avro schema. Basic workflow is producer includes the id in message and consumer uses that id to get the schema from registry. My question is on schema evolving issue.
Since consumer uses the id to get the schema and for every evolved schema, a new id is generated on producer’s side, why are there compatibility issues on consumer’s side if consumer can always get the updated schema based on the new id from message?
Beta Was this translation helpful? Give feedback.
All reactions