Fix message timestamp on produce v3 #188
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Produce v3 isn't filtering
undefined
timestamps and is sending timestamp0
(NaN converted) for all messages. This error should affect features that rely on the message timestamps and topics with "log.message.timestamp.difference.max.ms", the producer will throwINVALID_TIMESTAMP
error.Example on how to create a topic with the timestamp difference configuration: