Skip to content

Add Migration to Reindex all issues

What does this MR do and why?

2nd Part of 3 MRs as mentioned here

Added a migration to reindex all issues and respecting limit indexing.

Expected Runtime: 2 days

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Ensure elasticsearch is enabled
  2. Remove work_item_type_id column from an issue document
POST /gitlab-development-issues/_update/{id}
{
  "script": "ctx._source.remove('work_item_type_id')"
}
  1. Run the migration from rails console
  2. Go to elasticsearch and then query for that issue document and make sure that the work_item_type_id is present in the document

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #430149 (closed)

Edited by Siddharth Dungarwal

Merge request reports

Loading