Add NOT NULL to bulk_import_configurations

What does this MR do and why?

Adds NOT NULL constraint on sharding key column organization_id on table: bulk_import_configurations.

This merge request is the last step towards transforming the desired sharding key into a sharding key.

This involves the following changes:

  • Adding a not null constraint for the sharding key columns (organization_id).
  • Setting organization_id as sharding_key of bulk_import_configurations.

We are skipping model-level validations when adding NOT NULL for now: !189213 (comment 2480466972)

References

Screenshots or screen recordings

Before After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports

Loading