Delete Notes from original ES index
What does this MR do?
Whoops we missed this as part of #297646 (closed) - it's the last step.
Notes have already been moved over to a separate index and searches are verified to be using the new separate index.
This MR will remove all notes from the original index freeing up space
How to test
Verify that you have:
- Advanced Search setup and enabled (for searching and indexing)
- Data including merge requests loaded
Open a rails console and run the migration worker. You can follow the migration progress in the elasticsearch.log
file.
Elastic::MigrationWorker.new.perform
Screenshots (strongly suggested)
Note: I've unfortunately created my index freshly after the notes migration had completed, so it does not have notes in the original index. I'm pretty confident this will run as expected due to the previous Issues delete migration (which this migration was modeled after).
{"severity":"INFO","time":"2021-05-10T19:14:23.070Z","correlation_id":null,"message":"MigrationWorker: migration[DeleteNotesFromOriginalIndex] updating with completed: true"}
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
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