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
[Kernel] Update column mapping and schema evolution code to support usage with replace table (delta-io#4520)
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://github.com/delta-io/delta/blob/master/CONTRIBUTING.md
2. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP]
Your PR title ...'.
3. Be sure to keep the PR description updated to reflect all changes.
4. Please write your PR title to summarize what this PR proposes.
5. If possible, provide a concise example to reproduce the issue for a
faster review.
6. If applicable, include the corresponding issue number in the PR title
and link it in the body.
-->
#### Which Delta project/connector is this regarding?
<!--
Please add the component selected below to the beginning of the pull
request title
For example: [Spark] Title of my pull request
-->
- [ ] Spark
- [ ] Standalone
- [ ] Flink
- [X] Kernel
- [ ] Other (fill in here)
## Description
Update SchemaUtils and ColumnMapping with unit tests in order to support
REPLACE TABLE with column mapping + fieldId re-use in PR #2.
Specifically this involves the following changes (not necessarily
related, but combined in this PR)
1) When a connector provides its own column mapping info in the schema
pre-populated we require that it's complete (i.e. fieldId AND
physicalName must be present)
2) We add an argument to our schema validation checks
`allowNewNonNullableFields`. This is useful in cases where we can be
sure the table state has been completely cleared, and thus new non-null
fields are valid (like REPLACE).
3) We don't allow adding a new column with a fieldId less than the
maxColId. For now, do this proactively for safety. In the future in the
case of something like RESTORE in the future we will likely need a
config to bypass this check.
## How was this patch tested?
Updates unit tests.
Also, all the changes in this PR are used by
delta-io#4520 which adds a lot more E2E
tests with multiple schema scenarios.
## Does this PR introduce _any_ user-facing changes?
No.
0 commit comments