Stable partition bucket for a record IDENTITY (e.g. its ExternalID). Hashing the identity (not the
content) keeps a record in the SAME partition across syncs even when its content changes — so a
content edit shows up as a changed partition rather than a record hopping buckets. SHA-256 of the
id, first 4 bytes folded modulo partitionCount, gives an even, deterministic spread. Default 256
buckets is a sane balance (few enough rollups to store, fine-grained enough to skip most work).
Stable partition bucket for a record IDENTITY (e.g. its ExternalID). Hashing the identity (not the content) keeps a record in the SAME partition across syncs even when its content changes — so a content edit shows up as a changed partition rather than a record hopping buckets. SHA-256 of the id, first 4 bytes folded modulo
partitionCount, gives an even, deterministic spread. Default 256 buckets is a sane balance (few enough rollups to store, fine-grained enough to skip most work).