Add sharding-key on upcoming_reconciliations
What does this MR do and why?
This MR adds organization as sharding-key for upcoming_reconciliations
table.
namespace_id
is NOT NULL
for GitLab.com
, but NULL
on self-managed
instances (source code).
Thus, we add organization_id
as new NOT NULL
column and make it sharding-key.
Previous MR for reference: Add organization_id column (!154406 - merged)
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.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #462598
Edited by Bishwa Hang Rai