[v10.4.x] SQLStore: Disable redundant create and drop unique index migrations on dashboard table #86866
Conversation
![grafana-delivery-bot[bot]](https://avatars.githubusercontent.com/in/329617?s=60&v=4){kind=small}
grafana-delivery-bot
bot
requested review from
papagian,
diegommm and
idafurjes
and removed request for
a team
grafana-delivery-bot
bot
added
add to changelog
area/backend
backport
|
/deploy-to-hg |
|
|
Error building instance: Contact #proj-ephemeral-hg-instances if it is not a compile error. Logs handling pull request comment event: running grafana-build deb: executing command: stdout= stderr=go: downloading dagger.io/dagger v0.11.0 Stdout: |
|
/deploy-to-hg |
|
|
Error building instance: Contact #proj-ephemeral-hg-instances if it is not a compile error. Logs handling pull request comment event: running grafana-build deb: executing command: stdout= stderr=go: downloading dagger.io/dagger v0.11.0 Stdout: |
|
/deploy-to-hg --enterprise-ref backport-86857-to-v10.4.x |
|
|
Backport a5a3ee9 from #86857
What is this feature?
Fix migration failure when trying to create unique index on
dashboardtable fororg_id,folder_uid,titlecolumnswhen there is a folder and dashboard with the same title exist under the same folder like the following:
Migration failure
These index is redundant and there is follow up migrations dropping the index and create a unique index on:
org_id,folder_uid,title,is_foldercolumns instead.This fix replace the create and drop indexes to dummy migrations so that they do not have any effect.
Setups that the specific migrations are executed are not affected because the migrations are marked as executed in the database.
For new setups the migrations are executed (doing nothing) and marked as completed in the database.
Why do we need this feature?
[Add a description of the problem the feature is trying to solve.]
Who is this feature for?
[Add information on what kind of user the feature is for.]
Which issue(s) does this PR fix?:
Fixes #
Special notes for your reviewer:
Please check that: