8000 [BUG] Honor force when deleting catalogs and schemas by eddiethedean · Pull Request #60 · dmux/minilake · GitHub
[go: up one dir, main page]

Skip to content

[BUG] Honor force when deleting catalogs and schemas - #60

Merged
dmux merged 5 commits into
dmux:mainfrom
eddiethedean:fix/unity-catalog-delete-force-32
Oct 29, 2026
Merged

dmux merged 5 commits into
dmux:mainfrom
eddiethedean:fix/unity-catalog-delete-force-32

Conversation

@eddiethedean
Copy link
Copy Markdown
Collaborator

Summary

Make Unity Catalog catalog and schema deletion honor the force query parameter. Nonempty resources are preserved and rejected by default; force=true explicitly enables cascading deletion. The checks include registered UC objects, volume directories, and DuckDB objects created through raw SQL, and run under the DuckDB catalog lock before destructive changes.

Forced deletion also clears function and volume metadata and removes managed volume directories after the backing catalog or schema is deleted.

Fixes #32

Validation

  • Dockerized full suite: 410 passed
  • uv run ruff check src/ tests/
  • git diff --check

@eddiethedean
Copy link
Copy Markdown
Collaborator Author

Reviewed the full PR. The catalog attachment data-loss issue is fixed, the regression test passes, and all CI checks are green. Ready to merge.

@dmux dmux self-assigned this Oct 28, 2026
@dmux dmux added the bug Something isn't working label Oct 28, 2026
@dmux
dmux merged commit 4c33778 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] Catalog and schema deletion destroys tables when force=false

2 participants

0