8000 fix: cascade cleanup when deleting schemas and catalogs by eddiethedean · Pull Request #77 · dmux/minilake · GitHub
[go: up one dir, main page]

Skip to content

fix: cascade cleanup when deleting schemas and catalogs - #77

Merged
dmux merged 4 commits into
dmux:mainfrom
eddiethedean:codex/fix-issue-48-schema-cascade-cleanup
Oct 29, 2026
Merged

dmux merged 4 commits into
dmux:mainfrom
eddiethedean:codex/fix-issue-48-schema-cascade-cleanup

Conversation

@eddiethedean
Copy link
Copy Markdown
Collaborator

Summary

  • Cascade schema and catalog deletion through registered functions, volumes, and grants.
  • Remove managed volume data when its schema or catalog is deleted, and prevent orphaned directories from being adopted when parents are absent.
  • Add regression coverage for cleanup and recreating deleted names.

Validation

  • Ruff format and lint checks passed.
  • tests/unity_catalog/test_deletion_cascade.py: 2 passed.

Fixes #48

@eddiethedean
Copy link
Copy Markdown
Collaborator Author

All checks have passed. This PR is ready to merge.

@dmux dmux self-assigned this Oct 29, 2026
@dmux dmux added the bug Something isn't working label Oct 29, 2026
@dmux
dmux merged commit 89cae04 into dmux:main Oct 29, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Deleting schemas leaves orphaned functions and volumes

2 participants

0