-
Notifications
You must be signed in to change notification settings - Fork 13
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
Handle timestamp value in response from Bridge #107
Conversation
Signed-off-by: Lukas Kral <[email protected]>
Looking at the error message, I am assuming the test is failing because producer is setting the timestamp but consumer is not able to decode it, right? Because timestamp is optional not mandatory for the bridge. |
@ppatierno
where the second For Bridge producer we are not setting the timestamp neither:
Is it optional? I thought that it will be there always (but that's something I will need to test). |
@im-konge yeah sorry, I was stupid. Of course, on the consumer side it's always there. Even when the producer doesn't send it, the record will get the processed timestamp when it's ingested on Kafka and returned to the consumer. |
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.
LGTM.
@ppatierno yeah I was just testing it and I bumped into article about it. So yes, it will be there always. |
Signed-off-by: Lukas Kral <[email protected]>
* Handle timestamp value in response from Bridge Signed-off-by: Lukas Kral <[email protected]> * fix the ConsumerRecord toString() method Signed-off-by: Lukas Kral <[email protected]> --------- Signed-off-by: Lukas Kral <[email protected]>
After strimzi/strimzi-kafka-bridge#915 was added into Bridge, we need to handle it in our
ConsumerRecord
for HTTP response -> because without that, we are getting: