Add runner_machine_id column and partition index to ci_builds_metadata
What does this MR do and why?
Describe in detail what your merge request does and why.
This MR is the first of 2 MRs:
-
▶ Add runner_machine_id column and partition inde... (!108165 - merged) - Add runner_machine_id foreign key to p_ci_build... (!108167 - merged)
and does the following:
- Adds the
runner_machine_id
column to thep_ci_builds_metadata
partition metadata table; - Uses
prepare_async_index
to schedule an async indexing operation for the next weekend (docs), so that next week we can proceed with the rest of the operation (create index on the partition metadata tablep_ci_builds_metadata
and add the concurrent foreign key).
The rationale is discussed here: !108024 (comment 1227479248)
I needed to temporarily add the new column to IGNORED_FK_COLUMNS
because the foreign key will only be created in the follow-up !108167 (merged) (which will only be merged once this MR has been merged and the async index created over a weekend). !108167 (merged) will remove again the column from IGNORED_FK_COLUMNS
.
Part of #386755 (closed)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.