This is unsound, since two entries at different path/subspaces can have identical timestamps, digests and payload lengths.
Even if this was sound, that relation is not a good choice for many storage architectures: it is natural to model willow data as a mapping from SubspaceId-Path pairs to entry data, and such a mapping is not sorted by timestamp.
Suggested solution: make the will_sort field refer to ordering by SubspaceId, with Path as a tiebreaker.
In the WGPS, the
will_sort
field of theReconciliationAnnounceEntries
currently uses ordering by thenewer
relation on entries.This is unsound, since two entries at different path/subspaces can have identical timestamps, digests and payload lengths.
Even if this was sound, that relation is not a good choice for many storage architectures: it is natural to model willow data as a mapping from SubspaceId-Path pairs to entry data, and such a mapping is not sorted by timestamp.
Suggested solution: make the
will_sort
field refer to ordering by SubspaceId, with Path as a tiebreaker.