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

grpc custom metadata passthrough implementation #1097

Merged
merged 14 commits into from
Jul 16, 2024

Conversation

ankitk-me
Copy link
Contributor

Fixes #730

@ankitk-me ankitk-me marked this pull request as ready for review June 26, 2024 16:00
Copy link
Contributor

@jfallows jfallows left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR seems to be using text based metadata exclusively.

How do we plan to handle binary metadata via kafka message headers?
For example, how could we tell we need to decode a kafka message header as grpc binary vs text?

Btw, for end to end testing, don't we also need changes in kafka-grpc binding to support binary and text metadata?

Copy link
Contributor

@jfallows jfallows left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor initial feedback

jfallows
jfallows previously approved these changes Jul 10, 2024
@jfallows jfallows merged commit f3e344c into aklivity:develop Jul 16, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support grpc custom metadata pass through
3 participants