Skip to content

Add desired sharding keys for portfolio_management

Manoj M J requested to merge determine-desired-sharding-key-feature-category-portfolio_management into master

Add desired sharding keys for feature category portfolio_management.

These tables have been identified as a cell local tables. All cell local tables require a sharding key or a desired sharding key

A desired sharding key has been automatically selected for these tables. These keys were chosen as the desired sharding keys because the table has a :belongs_to relationship to a table that itself has a NOT NULL sharding key.

We have assigned a random backend engineer from groupproduct planning to review these changes.

Please confirm that:

  • each of these tables can be classified as cell local
  • the selected desired sharding key is appropriate
  • the backfill configuration for the desired sharding key is correct

When you are finished, please request a review from the database maintainer suggested by Danger. If you have any questions or concerns, reach out to @tigerwnz, @DylanGriffith or @manojmj.

If you would like to go through similar merged MRs so as to gather an understanding on this topic, you can use this link.

This change was generated by gitlab-housekeeper

Merge request reports