You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When rewriting a blob file, we need record the mapping from the original blob
file's block ID to the new blob file's physical block in the 'virtual block'
column. Previously the onus was on the user of the BlobFileWriter to call
AddVirtualBlockMapping for every blockID in the original file, even for
blockIDs that have no extant values.
This commit removes the onus from the caller and handles populating sparseness
within the implementation of BlobFileWriter.AddVirtualBlockMapping. This fixes
a bug in blob-file rewriting when multiple blocks map to the first physical
block. Additionally, this commit updates the virtual column entries for empty
virtual blocks to reflect the sparseness storing 0xFFFFFFFF in the column
(semantically equivalent to an entry mapping to the 0'th physical block with a
valueID offset of 0xFFFFFFFF).
0 commit comments