Update version for hashed_namespace migration

Dmitry Gruzdrequested to merge
update-hashed-namespace-migration into master

What does this MR do and why?

This is a follow-up from !113860 (merged)

I believe that we've missed a great optimization opportunity for the backfilling on notes. Currently we have:

  1. ee/elastic/migrate/20230203122938_backfill_internal_on_notes.rb
  2. ee/elastic/migrate/20230307092700_add_hashed_root_namespace_id_to_notes.rb
  3. ee/elastic/migrate/20230307102400_backfill_hashed_root_namespace_id_on_notes.rb

By moving add_hashed_root_namespace_id_to_notes before backfill_internal_on_notes we can avoid reindexing the same documents multiple times if all of these migrations are unapplied (like GitLab.com) and for self-managed customers that jump versions. That would reduce the backfill time from 18 to 9 days.

This should be safe since we have a guard check in the mappings helper.

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.

Edited by Dmitry Gruzd

Merge request reports