Repository navigation
docs: propose a unified Delta catalog for SQL and Spark - #90
Open
eddiethedean wants to merge 3 commits into
Open
eddiethedean wants to merge 3 commits into
eddiethedean wants to merge 3 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Managed tables currently store rows inside DuckDB, so Spark cannot read them. This documentation-only proposal describes sharing Delta-backed tables across both engines while retaining DuckDB for SQL.
Related to #89. The requested decision is whether to pursue a feasibility milestone; approving these documents does not approve a default change or migrate users.
The branch starts from upstream 1.9.1. No runtime, dependency, or package-version changes are included.
Validation: documentation whitespace, local links, and heading anchors pass. Writer compatibility, managed-table Spark interoperability, and performance benchmarks remain work for the feasibility milestone.
Implementation sequencing: phased implementation plan with dependencies, deliverables, validation evidence, and approval gates.