[Dev] Optimize ValidityMask
when reading from a ColumnDataCollection
#14416
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.
When we serialize the ColumnDataCollection, we will write the
validity_t *validity_mask
regardless of the validity being uninitialized or not.We do this because it's difficult to keep track of the validity status when appending multiple Vectors.
When we read this back however, we receive a ValidityMask that returns false for
AllValid
which could be costly as most execution paths of the engine have optimized paths forAllValid()
being true.Now we'll efficiently check the validity mask when reading and replace it will nullptr if all entries are valid, enabling the
AllValid() == true
optimized path for these vectors.