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.
Padding eligibility also needs to ignore NULL payloads. For
CHAR(4), a live"a"(1 byte) plus a NULL row with a 7-byte nested payload haschars.size() == 2 * 4, soshould_padding()returns false and this new call never executes. Debug then fails the live-row widthDCHECK; release forwards a 1-byteSlice, and a 4-byte CHAR short key reachesCHECK(index_size <= slice->size). Please make the predicate inspect non-NULL rows using the same unshifted map, and add a production-converter test for this compensating-size case; existing tests never exercise the new null-map branch.