-
Notifications
You must be signed in to change notification settings - Fork 589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audit configuration property validation across APIs #13443
Comments
https://redpandadata.slack.com/archives/C04RUGD1ENT/p1695843487574829 - |
This issue hasn't seen activity in 3 months. If you want to keep it open, post a comment or remove the |
@michael-redpanda guess this is still to be done, yes? |
This issue hasn't seen activity in 3 months. If you want to keep it open, post a comment or remove the |
#13442 examines the problem of validation of one property "replication factor" having different behavior when specified/change through Create Topics API vs Alter Topics Config API.
This ticket is to quickly audit the set of topic configurations and repeat the work in #13442 for any that also have inconsistent validation handling.
I do not expect that many configuration option validations will have the same issue as replication factor. Take compaction,deletion policy for example: these can simply be enabled or disabled at will. The same for scalar settings like retention times etc...
JIRA Link: CORE-1446
The text was updated successfully, but these errors were encountered: