You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
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
The text was updated successfully, but these errors were encountered: