ferrirW commented on issue #2: URL: https://github.com/apache/rocketmq-schema-registry/issues/2#issuecomment-1188988640
1. In our design, schema is a table like concept. When the schema or table structure changed, its version number will increase, but the ID should remain the same. As long as we promise that schema ID + version is unique, producer / consumer can use like "schemaId#version" to pointed the schema. At the same time, since we use the snowflake algorithm to realize unique ids, reducing the generation of ids can also avoid conflicts. 2. I totally agree that there needs to be some more detailed errorcodes. 3. yes, current version contains only the most basic functions including add, delete, update and get. So any extension to the interface is very welcome. -- 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]
