You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prompted by a discussion on a PR replacing Kafka consumer implementations with confluent-kafka, it turns out we do not back up the timestamp types of messages/records. (The kafka-python library had this as a separate field ConsumerRecord.timestamp_type; confluent-kafka has a 2-tuple for Message timestamps.)
How could this be improved?
Should timestamp types be backed up and restored?
The implementation seems relatively straightforward, the current timestamps could be extended with the type
Is this a feature you would work on yourself?
I plan to open a pull request for this feature
The text was updated successfully, but these errors were encountered:
What is currently missing?
Prompted by a discussion on a PR replacing Kafka consumer implementations with confluent-kafka, it turns out we do not back up the timestamp types of messages/records. (The kafka-python library had this as a separate field
ConsumerRecord.timestamp_type
; confluent-kafka has a 2-tuple forMessage
timestamps.)How could this be improved?
Is this a feature you would work on yourself?
The text was updated successfully, but these errors were encountered: