Repository navigation
feat: Classify new nullable columns and new tables as additive file changes - #788
Merged
Merged
Conversation
marianogappa
approved these changes
Oct 9, 2026
kodiakhq Bot
pushed a commit
that referenced
this pull request
Oct 9, 2026
🤖 I have created a release *beep* *boop* --- ## [4.9.0](v4.8.0...v4.9.0) (2026-10-09) ### Features * Classify new nullable columns and new tables as additive file changes ([#788](#788)) ([5685244](5685244)) ### Bug Fixes * Correct Parquet root_repetition description ([#789](#789)) ([112a935](112a935)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
2 participants
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.
Reports tables whose only changes are new nullable columns, and new tables, as automatically migratable with file behavior text instead of file schema changed, for Parquet and JSON always and for CSV only when the new columns are at the end of the row and the writer writes a header row (
skip_header: false, the default), because the CSV writer writes headers only then and CSV readers match columns by position.