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
{{ message }}
This repository has been archived by the owner on Nov 5, 2020. It is now read-only.
In order to achieve reusability in avro schemas, we have a couple options. We can use schema references on the .avsc level or we can use .avdl or .avpr, among possibly others.
Ultimately, the avro-maven-plugin resolves any schema references/dependencies and produces a single avro schema definition that is placed in it's generated java classes.
I propose that the plugin also write these resolved avro schema to self-contained .avsc in target/generated-sources/avsc/**, or similar.
This would be helpful as it would allow consumers of this plugin to then use these self-contained avro schema in down stream systems directly, rather than needing to pluck them out of the generated java classes.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In order to achieve reusability in avro schemas, we have a couple options. We can use schema references on the
.avsc
level or we can use.avdl
or.avpr
, among possibly others.Ultimately, the avro-maven-plugin resolves any schema references/dependencies and produces a single avro schema definition that is placed in it's generated java classes.
I propose that the plugin also write these resolved avro schema to self-contained
.avsc
intarget/generated-sources/avsc/**
, or similar.This would be helpful as it would allow consumers of this plugin to then use these self-contained avro schema in down stream systems directly, rather than needing to pluck them out of the generated java classes.
The text was updated successfully, but these errors were encountered: