Populate "next" desired sharding key for tables
We should come up with a keep that sets the "next" desired sharding key for tables which
- have a non-nullable parent association
- but the parent association does not have a fully backfilled
sharding_key
yet. It only has adesired_sharding_key
set now, but it will be eventually backfilled, and when that is completed, these tables can inturn backfill from that parent association.
We use awaiting_backfill_on_parent: true
to distinguish between these type of desired sharding keys and normal desired sharding keys.
And using this keep, we should generate MRs per feature category
Edited by Manoj M J