Skip to content

usage: widen usage_volume unique key to include vm_id #13909

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Alpha162 wants to merge 7 commits into
base: main
Choose a base branch
from
+5 −0
Open

usage: widen usage_volume unique key to include vm_id #13909

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
2fe71ff
usage: widen usage_volume unique key to include vm_id
Alpha162 Aug 18, 2026
1a96921
usage: add IDEMPOTENT_ADD_UNIQUE_KEY procedure for cloud_usage schema
Alpha162 Aug 18, 2026
d103780
usage: add IDEMPOTENT_DROP_UNIQUE_KEY procedure for cloud_usage schema
Alpha162 Aug 18, 2026
3a2b69b
usage: call the cloud_usage idempotent key procedures
Alpha162 Aug 18, 2026
5bfa692
usage: drop redundant IDEMPOTENT_ADD_UNIQUE_KEY procedure
Alpha162 Aug 18, 2026
e5dd472
usage: drop redundant IDEMPOTENT_DROP_UNIQUE_KEY procedure
Alpha162 Aug 18, 2026
79290bd
usage: use existing cloud_usage index procedures to widen the key
Alpha162 Aug 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions engine/schema/src/main/resources/META-INF/db/schema-42210to42300.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -646,3 +646,8 @@ CALL `cloud`.`IDEMPOTENT_ADD_COLUMN`('cloud.backup_schedule', 'isolated', 'TINYI

UPDATE `cloud`.`configuration` SET `value`=CONCAT(`value`, ', backupValidationCommandTimeout, backupValidationScreenshotWait, backupValidationBootTimeout')
WHERE `name`='user.vm.readonly.details' AND `value` IS NOT NULL;

-- Widen the unique key on cloud_usage.usage_volume to include vm_id, so the two volume
-- usage records introduced in 4.22.1 (cumulative and per-VM) can coexist. See #13399.
CALL `cloud_usage`.`IDEMPOTENT_DROP_INDEX`('id', 'cloud_usage.usage_volume');
CALL `cloud_usage`.`IDEMPOTENT_ADD_UNIQUE_INDEX`('cloud_usage.usage_volume', 'id', '(volume_id ASC, created ASC, vm_id ASC)');