Status: IN
Neither partitioning strategy offers both reliable routing and ordered access: range partitioning preserves key ordering but depends on maintaining parallel arrays in lockstep with invariants that are never verified (boundaries/partitions correspondence, adjacency assumptions in merge), while hash partitioning provides deterministic single-lookup routing but permanently destroys lexicographic key order, making range queries impossible.
Range partitioning is ordered but fragile, hash partitioning is robust but unordered — each strategy sacrifices the property the other provides
Depends on (SL): range-partitioning-routing-is-structurally-fragile, hash-mod-destroys-key-order