Blocker Description
Upgraded a kafka streams application from 2.6.0 to 2.7.0. Noticed that the events being produced had a "CreatedAt" timestamp = 0, causing downstream failures as we depend on those timestamps. Reverting back to 2.6.0/2.6.1 fixed this issue. This was the only change to the Kafka Streams application.
Consuming the event stream produced by 2.6.0 results in events that, when consumed using the `kafka-avro-console-consumer` and `--property print.timestamp=true` result in events prepended with the event times, such as:
CreateTime:1613072202271 <key> <value> CreateTime:1613072203412 <key> <value> CreateTime:1613072205431 <key> <value>
etc.
However, when those events are produced by the Kafka Streams app using 2.7.0, we get:
CreateTime:0 <key> <value> CreateTime:0 <key> <value> CreateTime:0 <key> <value>
I don't know if these is a default value somewhere that changed, but this is actually a blocker for our use-cases as we now need to circumnavigate this limitation (or roll back to 2.6.1, though there are other issues we must deal with then). I am not sure which unit tests in the code base to look at to validate this, but I wanted to log this bug now in case someone else has already seen this or an open one exists (I didn't see one though).
Attachments
Attachments
Issue Links
- is duplicated by
-
KAFKA-12643 Kafka Streams 2.7 with Kafka Broker 2.6.x regression: bad timestamp in transform/process (this.context.schedule function)
-
- Resolved
-
- links to