Document merge_adjacent_files x schema evolution#341
Merged
szarnyasg merged 1 commit intoApr 23, 2026
Merged
Conversation
Collaborator
|
Thanks for the contribution, @zhming0! |
zhming0
deleted the
ming/document-merge_adjacent_files-x-schema-evolution
branch
Contributor
Author
|
Thank you @szarnyasg! I have also raised a PR to address this limitation: duckdb/ducklake#1049, <- if this is accepted I will come back to update the doc too. 😁 |
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.
Document
ducklake_merge_adjacent_files's limitation when schema evolution happens. I come across this limitation when I useducklake_merge_adjacent_files.