-
Notifications
You must be signed in to change notification settings - Fork 160
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
Modularization: avro module #115
Comments
@slinkydeveloper: I do have implementation of EventFormat interface for avro. However, the implementation class has a setter method for Avro schema since this not defined in EventFormat interface. Hence, following code would be used to get hold of format and serialize.
Let me know your thoughts. |
Which schema? |
This is avro schema. That is |
avro schema of what? of Cloudevents? The one from the spec https://github.com/cloudevents/spec/blob/v1.0/spec.avsc? |
Thats correct. It *.avsc schema |
Shouldn't this be loaded statically? Can we ship this schema as a resource in the package and then load it statically? |
The schema at https://github.com/cloudevents/spec/blob/v1.0/spec.avsc is just a spec, whereas real schema would have much more details (in |
TBH I'm not an expert of avro, so I can't tell. What I can say is that it sounds weird to me to mutate the internal state of |
@subanasif https://github.com/cloudevents/spec/blob/v1.0/spec.avsc is compiled into Java before shipping, so dynamically loading it is not necessary (although possible). That Avro spec is used by other CE clients, so I don't think it can be changed as long as compatibility with CE 1.0 is desired. |
I'm not sure that's what is being suggested. |
any update on this issue? |
Is there any update on if/when this will be released? |
This is just waiting for a contribution to come 😄 |
Just let you know I have been working on an avro serde impl these days. |
This module implements the Avro Event Format.
avro
This module depend on api one.
When someone wants the avro format to create or read events, they add this module and they concern about potential conflicts with pre-existing dependencies in their projects.
The text was updated successfully, but these errors were encountered: