Skip to content

Ensure that each defined sharding key has a foreign key

Tiger Watson requested to merge assert-sharding-keys-have-foreign-keys into master

What does this MR do and why?

Adds an extra check to the sharding key tests to ensure that every sharding key column has a foreign key to the nominated table.

There are valid reason reasons for some sharding keys to not have a foreign key, so an allowlist is provided for these columns. If a column is added to the allowlist, we expect it to have no foreign key at all.

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.

Edited by Tiger Watson

Merge request reports