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] [CORE-3008] schema_registry: Improve handling of deleted schema #19972

Merged

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #19944

Rob Blafford and others added 3 commits June 24, 2024 20:47
store::get_versions was ignoring include_deleted, which meant that
the new schema was detected as existing, but not a candidate for
being added as a new version.

A test was fixed up, as schema id 1 is not compatible with id v2,
compatibility must be set to NONE before adding back id 1, as it
will become version 3.

Signed-off-by: Ben Pope <ben@redpanda.com>
(cherry picked from commit c8a0a6e)
When the last version is soft-deleted, the config should be cleared.

Signed-off-by: Ben Pope <ben@redpanda.com>
(cherry picked from commit d97925d)
Signed-off-by: Ben Pope <ben@redpanda.com>
(cherry picked from commit 4261670)
@vbotbuildovich vbotbuildovich added this to the v23.3.x-next milestone Jun 24, 2024
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Jun 24, 2024
@BenPope BenPope merged commit 8e1b350 into redpanda-data:v23.3.x Jun 25, 2024
18 checks passed
@BenPope BenPope self-assigned this Jun 25, 2024
@BenPope BenPope modified the milestones: v23.3.x-next, v23.3.18 Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/redpanda kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants