merlimat commented on issue #1551: Json schema codec
   > I suppose I could hack in a default "is compatible" check that literally 
checks if they are equal which would require schema updates to happen via the 
REST interface. This would make upgrades hard/impossible to do seamlessly.
   I think for JSON we should first check if there's a schema and if the schema 
type is the same as a starter. For evolution, I guess the basic check would be 
to validate there are no type mismatchs. 
   It's typically ok to add/remove fields (provided we have configured Jackson 
to do so - and we should verify that), but changing type would lead to errors 
in deserialization.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to