Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Assume confluent wire format when deserializing a Schedule #33

Open
Thomas-Heslin opened this issue Apr 4, 2018 · 2 comments
Open

Assume confluent wire format when deserializing a Schedule #33

Thomas-Heslin opened this issue Apr 4, 2018 · 2 comments

Comments

@Thomas-Heslin
Copy link
Contributor

Currently Schedule messages are stored as Avro binary format.

It would be ideal for testing if the Confluent wire format was used instead, otherwise messages can only (realistically) be sent to the KMS programmatically.

This will also allow for integration with the Schema Registry.
@paoloambrosio-skyuk
Copy link
Contributor

Good idea. Shall we make it optional?

@lacarvalho91
Copy link
Contributor

@paoloambrosio-skyuk I was wondering this...would be tricky I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lacarvalho91 @paoloambrosio-skyuk @Thomas-Heslin