-
Notifications
You must be signed in to change notification settings - Fork 83
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
feat: provide support for Kafka message keys different than "string?" #314
base: main
Are you sure you want to change the base?
Conversation
Implements cloudevents#313 Signed-off-by: Jon Abaunza <j.abaunza@lantek.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of comments to streamline changes later, but I won't have time to review the actual code until next week.
src/CloudNative.CloudEvents.Kafka/PartitionKeyAdapters/BinaryGuidPartitionKeyAdapter.cs
Outdated
Show resolved
Hide resolved
…reaking change Signed-off-by: Jon Abaunza <j.abaunza@lantek.com>
f1855f3
to
ed04c9f
Compare
(Just to keep communicating - this is still on my plate, but keeps being bumped by higher priority things. I promise I'll get to it eventually...) |
I tried 2 different approaches for my same problem:
The cloud event had extended properties with the tenant information and due to a lack of proper examples I thought it would not be possible to get a hold of that tenant information using Dapr (all examples seemed to handle the payload of the cloud event and not the whole cloud event). I turns out that by not using the middleware added with ".UseCloudEvents()" and parsing the cloud event directly using the extension methods provided in this repository did the trick. Therefore, the Pull request won't be necessary from my part, although I think that other people could find it interesting (specially for binary key support). Some notes regarding the dapr implementation |
Thanks so much for the update - that's really good to know. I was hoping to review this in the next couple of days, but I was getting queasy about it, knowing how little I know about Kafka. I suggest we just leave the PR open for a little while, and see whether it attracts any attention from other users. Does that work for you? |
It's fine for me.
Thank you for looking into it
El mié, 9 oct 2024, 8:34, Jon Skeet ***@***.***> escribió:
… Thanks so much for the update - that's really good to know. I was hoping
to review this in the next couple of days, but I was getting queasy about
it, knowing how little I know about Kafka.
I suggest we just leave the PR open for a little while, and see whether it
attracts any attention from other users. Does that work for you?
—
Reply to this email directly, view it on GitHub
<#314 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB7WOGN5LURL7YN3TLBZJDTZ2TE6ZAVCNFSM6AAAAABO4XF7AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBRGQZTINZZGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This pull request implements support for Kafka Message key types other than "string?".