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
stats: fix "non-nullable col with no value" for multiple column families
This commit fixes an edge case in the timestamp-advancing mechanism of
the inconsistent scans that are used by the table statistics collection.
In particular, previously on a table with multiple column families it
was possible for the scan to stop in the middle of a SQL row, and if
that row happens to exist at the old timestamp but to no longer exist at
the new timestamp, we'd hit an internal error. The bug is now fixed by
setting WholeRowsOfSize option of the BatchRequest if we're scanning
a table with multiple column families which guarantees that the scan at
each timestamp will stop only at the ends of SQL rows.
To reproduce this behavior I extended an existing test that stresses the
timestamp-advancing mechanism.
Release note (bug fix): Previously, on a table with multiple column
families CockroachDB could encounter "Non-nullable column "‹×›:‹×›"
with no value" error during table statistics collection in rare cases.
The bug has been present since v19.2 and is now fixed.
0 commit comments