Correct issue_search_data table_size dictionary entry to medium

V K Adhithiya Kumarrequested to merge
gitlab-community/gitlab-org/gitlab:dev-adhithiya/629647-issue-search-data-table-size-medium into master

What does this MR do and why?

db/docs/issue_search_data.yml carries table_size: small. Per database_dictionary.md, a partitioned table is classified by its largest partition. The largest issue_search_data partition is 42.55 GiB, which is in the medium band (< 50 GB), so the current value is wrong.

This MR sets table_size: medium. The deliverable is dictionary accuracy: this file is what humans and tooling read to answer "how big is this table".

What this change does and does not bind

To avoid the assumption recorded in the parent epic, here is exactly which RuboCop migration cops are affected:

Cop Reads Bound by medium?
Migration/PreventIndexCreation large_or_over_limit_tables plus its own FORBIDDEN_TABLES constant Already bound today via the constant, which hardcodes :issue_search_data. Unchanged by this MR.
Migration/ChangeColumnNullOnHighTrafficTable large_or_over_limit_tables No
Migration/CreateTableWithForeignKeys large_or_over_limit_tables No
Migration/PreventAddingColumns over_limit_tables No

keeps/update_table_sizes.rb only maps large and over_limit into rubocop/rubocop-migrations.yml; medium maps to neither. So this change closes no migration-safety gap and alters no cop behaviour. If the team wants the remaining three cops to bind this table, that is a separate decision about whether a 42.55 GiB partition should be treated as large, and it belongs to the Database Frameworks group.

Out of scope

  • Editing rubocop/rubocop-migrations.yml (generated by the housekeeper).
  • Changing classification thresholds or the PreventIndexCreation constant.
  • The housekeeper keep that prevents this entry from self-healing (tracked in a sibling issue of the parent epic).
  • Any change to the table itself.

References

Closes #629647

Parent epic: &23629

MR acceptance checklist

  • This MR has been reviewed against the MR acceptance checklist.
  • This contribution was prepared with the help of an AI assistant. I reviewed the changes and take responsibility for them.

Merge request reports