Skip to content

Synchronously add vulnerabilities_reads indexes

What does this MR do and why?

In a previous MR we added the two indexes asynchronously.

We need to add the indexes synchronously to complete the async index addition process outlined in the docs:

The indexes we added are copies of two existing indexes, with just the new has_vulnerability_resolution column appended. Therefore, we can also remove those now redundant indexes.

  • The redundant indexes
    • index_vulnerability_reads_common_attrs_and_detection_for_groups
    • index_vulnerability_reads_common_finder_query_2

There was also a copy/paste issue with the down method in the async migration that I corrected.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Verification that async migration is complete

Before async migration After async migration
image image

Changelog: changed
Resolves: #493285 (closed)
Epic: &15036 (closed)

Edited by Michael Becker

Merge request reports

Loading