MatrixHB opened a new issue, #28: URL: https://github.com/apache/rocketmq-schema-registry/issues/28
Here are all the compatibility strategies of schema evolution. Transitivity specifies the compatibility check scope for each change. Compatible strategy | Permitted changes | Transitivity | Upgrade order -- | -- | -- | -- BACKWARD | Delete fields Add optional fields | Last version | Consumers BACKWARD_TRANSITIVE | Delete fields Add optional fields | All previous versions | Consumers FORWARD | Add fields Delete optional fields | Last version | Producers FORWARD_TRANSITIVE | Add fields Delete optional fields | All previous versions | Producers FULL | Modify optional fields | Last version | Any order FULL_TRANSITIVE | Modify optional fields | All previous versions | Any order NONE | All changes are accepted | Disabled | Depends The default strategy is BACKWARD, which is already implemented by `CommonUtil#validateCompatibility`. Please supplement the other 5 strategies. Also, it is better to extract ` CommonUtil#validateCompatibility` and become an independent class. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
