-
Notifications
You must be signed in to change notification settings - Fork 398
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
Feature Request - Support for Message Headers #414
Comments
It is definitely something I want to add. I can't tell when I will have time right now to dedicate to it because of how my time at the office has had to be spent, but it is on my radar. Hopefully I will have some time soon but will also be very, very happy to take a contribution for this. |
@webmakersteve what's necessary to make this happen? I could try to take a look at it, but the codebase is pretty foreign to me |
Looks like message headers are not supported in C++ yet, and the underlying bindings use the C++ version of |
It looks like the C++ library has a PR added support for headers 7 days ago: |
Please! This would be a great feature! |
I have this PR open #478 needs a few changes once the librdkafka changes are merged but it should follow it mostly. |
Updates to the PR have been made with the new merged changes |
👍 |
This is resolved with 6065784 |
Still not getting headers in message. |
The underlying library has support for kafka message headers: confluentinc/librdkafka#1480.
It would be nice if you could expose the headers to the node library for both consumers and producers. We are looking at using them to store event metadata which we can use to debug issues in the case where our avro messages cannot be deserialised properly.
Thank you.
The text was updated successfully, but these errors were encountered: