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
We've noticed that our kafka messages arriving with time=-1. We were able to work around this by changing our kafka brokers' log.message.timestamp.type setting from the default of CreateTime to LogAppendTime. However, we'd prefer that kafka messages get stamped with the creation time, which we believe requires changes to the producer client.
The text was updated successfully, but these errors were encountered:
Yes, this is a missing feature. Afkak currently produces to the broker using Message/MessageSet v0, which does not include a timestamp. We have work planned to implement Message/MessageSet v1 and Record/RecordBatch (which replace Message/MessageSet), but I don't have a timeline for it. Coordinated consumers are higher priority for us.
We've noticed that our kafka messages arriving with time=-1. We were able to work around this by changing our kafka brokers' log.message.timestamp.type setting from the default of CreateTime to LogAppendTime. However, we'd prefer that kafka messages get stamped with the creation time, which we believe requires changes to the producer client.
The text was updated successfully, but these errors were encountered: