Closed onepas closed 11 months ago
You should configure this property for the topic in question - message.timestamp.difference.max.ms
. Or set broker defaults that are very large to not encounter this issue for autocreated topics
What @GMaystorski says.
When you run the first query, no data is written into a topic, and thus the query works (the query is directly answered over data in RocksDB state stores). -- For the "emit changes" query, ksqlDB executes the query differently. But the error is not related to ksqlDB itself, but it's a Kafka configuration thing.
If messages retain in
ksql_fraud_whitelist
topic > 5 days, I gotInvalidTimestampException
when run emit changes queries.