Skip to content
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

[v23.3.x] cluster: don't apply invalid property change in topic_table (Manual backport) #23227

Merged

Conversation

WillemKauf
Copy link
Contributor

Manual backport of #23191. Merge conflict due to other unrelated migration additions in topic_table.cc.

Closes #23222.

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v24.2.x
  • v24.1.x
  • v23.3.x

Release Notes

Bug Fixes

  • Fixes a bug that resulted in persisting an invalid topic_properties configuration in the topic_table.

We check that the updated topic properties post
`topic_table::apply(update_topic_properties_cmd)` is valid with the
`schema_id_validation_validator`. However, this early `co_return` with an
error code does not actually prevent the invalid configuration from being
persisted in the `topic_table`.

Rework the logic in `topic_table::apply()` to prevent persisting of an invalid
configuration.

(cherry picked from commit 3a36f7a)
To ensure updates made from invalid `update_topic_properties_cmd` are not
persisted in `topic_properties`.

(cherry picked from commit 6da3157)
@piyushredpanda piyushredpanda merged commit 4b6e255 into redpanda-data:v23.3.x Sep 9, 2024
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants