Repository navigation
Conversation
- Extract the latest instance of that column name from historical schemas - Required columns will be come non-required - The parent field must already be present in the schema - Add spark procedure call to run undelete
This is common logic that is a little confusing at first glance. Also adds a hard failure in the case that the parent field is, for some reason, not available in the schema (this should be impossible, and if it happens, will return a null pointer)
Non-null defaults are only available in v3, so set the version in the test.
34b191a to
86b649b
Compare
- Add function to check whether data had been written for a col after the col was deleted - Fail to undelete a required col if data was written after it had been deleted - Add set_nullable parameter to force those cols as nullable, bypassing the failure (and allowing you to undelete a reqd col)
|
@steveloughran @gtrettenero @yingjianwu98 the old PR was auto-closed so I had to open a new one with the changes. There are two changes:
This more closely matches the Iceberg spec. |
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
set_nullableto allow required columns missing data to be undeleted and made nullable