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

[v24.1.x] CORE-5083 schema_registry: last subject deletes schema #21259

Merged

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #20847

pgellert added 2 commits July 5, 2024 16:35
Add support to `store::subject_versions_has_any_of` for including
deleted subject versions.

(cherry picked from commit 1edb81a)
When the last subject version corresponding to a schema is deleted,
Schema Registry should also remove the schema.

On the topic, the schema is already considered deleted when the last
subject version is deleted, and compaction takes care of removing it.
However, without this change, compaction needs to happen and then a node
restart needs to happen before the schema is removed from memory. This
is not ideal for use cases where schemas are frequently created and
deleted (eg. Serverless), so instead we can remove the schema from
memory when its last subject version is deleted.

(cherry picked from commit d85de7b)
@vbotbuildovich vbotbuildovich added this to the v24.1.x-next milestone Jul 5, 2024
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Jul 5, 2024
@vbotbuildovich vbotbuildovich requested a review from pgellert July 5, 2024 16:35
@pgellert pgellert merged commit 96c7514 into redpanda-data:v24.1.x Jul 8, 2024
19 checks passed
@BenPope BenPope modified the milestones: v24.1.x-next, v24.1.10 Jul 19, 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.

3 participants