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.

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

Support for Confluent Schema Registry? #288

Open
DaveSlinn opened this issue Aug 23, 2019 · 3 comments
Open

Support for Confluent Schema Registry? #288

DaveSlinn opened this issue Aug 23, 2019 · 3 comments
Labels
enhancement Feature request

Comments

@DaveSlinn
Copy link

DaveSlinn commented Aug 23, 2019

We are using https://github.com/takebayashi/fluent-plugin-avro to format our messages as Avro, but when sending to our kafka cluster, we need to prefix the avro data with 5 bytes to conform with the Confluent Schema Registry, as described here:

https://docs.confluent.io/current/schema-registry/serializer-formatter.html#wire-format

Is this possible? Is there a buffer or filter plugin that allows us to modify the raw bytes sent to Kafka after it has been formatted but before it is sent?

@rverma-jm
Copy link

@DaveSlinn did you find any solution for your usecase?

@DaveSlinn
Copy link
Author

Yes, a co-worker of mine forked the Avro plugin and added the ability to specify the confluent schema id. His forked repo is here: https://github.com/mstinglin/fluent-plugin-avro. We've been using it for months now. Works great.

@github-actions
Copy link

github-actions bot commented Jul 6, 2021

This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days

@github-actions github-actions bot added the stale label Jul 6, 2021
@kenhys kenhys added enhancement Feature request and removed stale labels Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request
Projects
None yet
Development

No branches or pull requests

3 participants