-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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] Add support for sending additional metadata in the MessagingInterface
#4472
Comments
I am interested in this |
Hey @tanbirali thanks for your interest. |
whenever I am running the docker-compose up -d all the services are working but the hyperswitch-hyperswitch-server-1 is exiting everytime starting the container, how can I fix this |
Hey @tanbirali , Also these are the steps for running hyperswitch locally via docker compose you can walk through them again if anything is amiss... There were some similar issues reported and solved in the discord can check if your issue is present there |
Hey @tanbirali , Are you still interested/working on this, |
I am working on it, will try to create a PR soon |
Sorry I am not able to run the project locally, I tried having a convo in the discord community, something or the other is not working for me, sorry for delaying it, I am trying in the mean time if anyone is willing to take this issue, please assign it to the individual |
Hey @tanbirali no worries, I'll keep the issue unassigned for now. |
Feature Description
In the current implementation of message interface I can only send a Message & a timestamp associated with the message,
There is no accomodation to send additional metadata about the message which isn't part of the data but could be propogated to the downstream implementations,
These could be used downstream as kafka headers or redis hashes or partition keys.
Possible Implementation
metadata can be a simplistic
HashMap<String, String>
and can be either accomodated as a new param in theMessagingInterface
or a new method on theMessage
Interface.The implementers of MessageInterface can handle it as follows
Send the metadata as headers
Log the metadata as a separate key along with the raw data
Have you spent some time checking if this feature request has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered: