Skip to content

fix(sonarqube): tolerate missing migration indexes#9012

Merged
klesh merged 1 commit into
apache:mainfrom
frederic-huebner:fix/sonarqube-migration-index
Jul 27, 2026
Merged

fix(sonarqube): tolerate missing migration indexes#9012
klesh merged 1 commit into
apache:mainfrom
frederic-huebner:fix/sonarqube-migration-index

Conversation

@frederic-huebner

@frederic-huebner frederic-huebner commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Make Dalgorm.DropIndexes idempotent by skipping absent indexes. This prevents MySQL error 1091 when the SonarQube and domain migrations at version 20260701000000 encounter legacy tables without their component indexes.

The regression test removes both legacy indexes before applying the two migrations, then verifies data preservation, text component columns, and absent indexes.

Does this close any open issues?

Closes #9011

Other Information

Validated with the targeted MySQL-backed regression, the full SonarQube E2E package, make lint, and make migration-script-lint.

@klesh klesh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Thanks for your contribution.

@klesh
klesh merged commit 7f7cf09 into apache:main Jul 27, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug][SonarQube] Migration fails when issue code block component index is absent

2 participants