-
-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avro schema generation: allow override namespace with new @AvroNamespace
annotation
#310
Comments
As things are, If anyone has time to try a PR I'd be happy to help, but I do not have time to work on this directly myself. One small thing about possible implementation: this should be an opt-in feature, for backwards compatibility. |
…ield namespace. Current namespace value is Java package name. This annotation allows to override its name.
…ield namespace. Current namespace value is Java package name. This annotation allows to override its name.
…ield namespace. Current namespace value is Java package name. This annotation allows to override its name.
…ield namespace. Current namespace value is Java package name. This annotation allows to override its name.
I think I found simple way how to override default Avro namespace value with a new, custom, annotation. Please , see #324. |
…ield namespace. Current namespace value is Java package name. This annotation allows to override its name.
…ield namespace. Current namespace value is Java package name. This annotation allows to override its name.
@AvroNamespace
annotation
Will be released as part of 2.14.0. |
I was hoping to override the namespace used in the schemas generated by
AvroSchemaGenerator
for my POJOs, as opposed to the package name that is used (as it does not make sense to the consumers of my topic, outside of my application).I cannot workout a means to do this, I tried
@JsonRootName(value = "ClassName", namespace = "my.domain")
but that is not picked up, is there any other means to achieve this?Note this is not the same as
@JsonAlias
, I would like to control the namespace, not thealiases
.Code currently used:
The text was updated successfully, but these errors were encountered: