Resolve "Set namespaces.traversal_ids for production gitlab-org group"
What does this MR do?
Performs a data migration to insert values in to the namespaces.traversal_ids column, only on production. This column is the path of namespaces IDs between the root ancestor and a namespace.
The SQL query is produced by TraversalHierarchy.new(Namespace.find(9970)).sync_traversal_ids!
can we start queueing background migrations to populate this field for all namespaces everywhere
This describes the second part of the production rollout process. Rolling this migration out for all namespaces is going to take days so we don't place undue pressure on the database.
In general we're proceeding cautiously given the complexity of the change, while also trying to move efficiently as this line is part of a rapid action.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #325509 (closed)