feat: recognize message.timestamp.after.max.ms and before.max.ms sett… - #1
Merged
pratikmallya merged 1 commit intoSep 10, 2026
Conversation
…ings These Kafka 3.6+ topic configs bound how far a message timestamp can diverge from broker time in either direction. topicctl's config validator didn't have entries for them, so any topic YAML explicitly setting these keys failed with "not recognized topic config setting" even though brokers (including Confluent Cloud) support and return them (see segmentio#191). Add validators using the same non-negative int64 pattern as sibling settings like delete.retention.ms.
Collaborator
Author
|
copy of segmentio#264 |
ozan-gnome
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…ings
These Kafka 3.6+ topic configs bound how far a message timestamp can diverge from broker time in either direction. topicctl's config validator didn't have entries for them, so any topic YAML explicitly setting these keys failed with "not recognized topic config setting" even though brokers (including Confluent Cloud) support and return them (see segmentio#191).
Add validators using the same non-negative int64 pattern as sibling settings like delete.retention.ms.