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
We created a proprietary Gradle plugin to assist developers in managing message formats and compatibility. Developers create or edit .avsc files locally like the one below, and Gradle will check the schema compatibility against Schema Registry using its REST interface, and if the schema is compatible, generate Java classes of the corresponding event schema with avro-tools. Next, the developer will be able to create a pull request for the new schema, and once the code change is approved and merged, our build tool will use Gradle to conduct one more compatibility check against Schema Registry, and then actually update the schema in Schema Registry, and release a respective Jar to our local Maven repository
We don't have anything like that. It could be every useful in terms of community as well as development process. We could integrate it in the Travis script to apply advance checks before publishing a new version.
The text was updated successfully, but these errors were encountered:
Quoting a blogspot from confluent blog.
We don't have anything like that. It could be every useful in terms of community as well as development process. We could integrate it in the Travis script to apply advance checks before publishing a new version.
The text was updated successfully, but these errors were encountered: