Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P1] Make the row-append APIs const-aware too
This helper is only called by the two merge paths, but
MutableBlock::add_row()and bothadd_rows()overloads still append directly to_columns. Those destinations can also remainColumnConst: for example,_partition_block()seeds a persistent buffer within_block->clone_empty(), andColumnConst::clone_resized(0)preserves the first block's nested value. After the first append, a later valid block with the same type but a different constant value is rejected byColumnConst::insert_indices_from()(and a full source is also rejected by the sibling append methods). Please extend the shared append handling so both the destination and any const source are materialized, or are otherwise handled without assuming one per-block value persists across later blocks, and cover twoadd_rows()calls with different constants. Otherwise the same representation mismatch still breaks partitioned-join/local-exchange accumulation.