Draft: POC: Add next desired sharding key
What does this MR do and why?
This is a draft MR to show the changes that can be committed by executing the new keep DetermineNextDesiredShardingKeyFeatureCategory
in !139747 (8d0a261f)
This commits 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 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.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.