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

Allow CDF scans with schema evolution #523

Open
OussamaSaoudi-db opened this issue Nov 22, 2024 · 2 comments · May be fixed by #554
Open

Allow CDF scans with schema evolution #523

OussamaSaoudi-db opened this issue Nov 22, 2024 · 2 comments · May be fixed by #554
Labels
enhancement New feature or request

Comments

@OussamaSaoudi-db
Copy link
Collaborator

Please describe why this is necessary.

TableChanges today asserts that the schema for the entire range be the same. This condition can be relaxed to allow new nullable columns to be added to the start schema, or toggling the nullability for an existing field to true.

Describe the functionality you are proposing.

Schema enforcement at TableChanges construction and during log replay must accept data with a schema that is missing a nullable field and must fill that nullable field in when producing rows.

Additional context

No response

@scovich
Copy link
Collaborator

scovich commented Dec 5, 2024

We should also ignore changes in schema metadata -- at least, the user-provided ones that Delta spec doesn't have any opinion about. I'm less clear whether we should tolerate changes in column mapping table properties?

@OussamaSaoudi-db
Copy link
Collaborator Author

@scovich Sorry for missing this comment! Seems that the only thing delta checks in the schema is the struct type and the partition columns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants