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
Describe the solution you'd like
In modern software design, often, data contracts/things that describe data are stored in schema registry. Instead of fieldDefinitions in the zingg conf let us reference a schema-registry url and schema name. This helps us centralize data descriptions in one place, and not have to re-define in another place.
Describe alternatives you've considered
Alternative is to use POCO classes defined in java... Glue schema registry etc. But avro schema is the cleanest solution.
Is your feature request related to a problem? Please describe.
Avro is described here in this documentation: https://avro.apache.org/docs/1.10.2/idl.html#minutiae_annotations
You can use java-style decorators to add details to your fields.
This is an example of an avro schema.
It compiles to a json:
It gets deployed to confluent schema registry and you can retrieve it with a simple
curl
:Describe the solution you'd like
In modern software design, often, data contracts/things that describe data are stored in schema registry. Instead of
fieldDefinitions
in the zingg conf let us reference aschema-registry
url and schema name. This helps us centralize data descriptions in one place, and not have to re-define in another place.Describe alternatives you've considered
Alternative is to use POCO classes defined in java... Glue schema registry etc. But avro schema is the cleanest solution.
Additional context
Since schema is stored in the registry, there is no need to repeat this information in the conf.
Here's the docker image to host your own schema registry. https://hub.docker.com/r/confluentinc/cp-schema-registry
The text was updated successfully, but these errors were encountered: