metabase/resources/migrations/060_update_migrations.yaml

databaseChangeLog:
  - objectQuotingStrategy: QUOTE_ALL_OBJECTS

  - changeSet:
      id: v60.2026-02-13T21:43:00
      author: epaget
      comment: Add dimensions column to measure table
      changes:
        - addColumn:
            tableName: measure
            columns:
              - column:
                  name: dimensions
                  type: ${text.type}
                  remarks: JSON array of persisted dimension definitions (id, display-name, types)
                  constraints:
                    nullable: true
      rollback:
        - dropColumn:
            tableName: measure
            columnName: dimensions

  - changeSet:
      id: v60.2026-02-13T21:43:01
      author: epaget
      comment: Add dimension_mappings column to measure table
      changes:
        - addColumn:
            tableName: measure
            columns:
              - column:
                  name: dimension_mappings
                  type: ${text.type}
                  remarks: JSON array of dimension-to-field mappings (dimension-id, target, table-id)
                  constraints:
                    nullable: true
      rollback:
        - dropColumn:
            tableName: measure
            columnName: dimension_mappings

  - changeSet:
      id: v60.2026-02-13T21:43:02
      author: epaget
      comment: Add dimensions column to report_card table for metrics
      changes:
        - addColumn:
            tableName: report_card
            columns:
              - column:
                  name: dimensions
                  type: ${text.type}
                  remarks: JSON array of persisted dimension definitions (id, display-name, types)
                  constraints:
                    nullable: true
      rollback:
        - dropColumn:
            tableName: report_card
            columnName: dimensions

  - changeSet:
      id: v60.2026-02-13T21:43:03
      author: epaget
      comment: Add dimension_mappings column to report_card table for metrics
      changes:
        - addColumn:
            tableName: report_card
            columns:
              - column:
                  name: dimension_mappings
                  type: ${text.type}
                  remarks: JSON array of dimension-to-field mappings (dimension-id, target, table-id)
                  constraints:
                    nullable: true
      rollback:
        - dropColumn:
            tableName: report_card
            columnName: dimension_mappings

  - changeSet:
      id: v60.2026-03-06T12:00:00
      author: bcm
      comment: Create source_replacement_run table to track async source replacement executions
      changes:
        - createTable:
            tableName: source_replacement_run
            remarks: Table to track source replacement executions and their status
            columns:
              - column:
                  name: id
                  type: int
                  remarks: Unique ID
                  autoIncrement: true
                  constraints:
                    primaryKey: true
                    nullable: false
              - column:
                  name: source_entity_type
                  type: varchar(50)
                  remarks: "Type of the source entity (card or table)"
                  constraints:
                    nullable: false
              - column:
                  name: source_entity_id
                  type: int
                  remarks: "ID of the source entity"
                  constraints:
                    nullable: false
              - column:
                  name: target_entity_type
                  type: varchar(50)
                  remarks: "Type of the target entity (card or table)"
                  constraints:
                    nullable: false
              - column:
                  name: target_entity_id
                  type: int
                  remarks: "ID of the target entity"
                  constraints:
                    nullable: false
              - column:
                  name: status
                  type: varchar(50)
                  remarks: "Current status (started, succeeded, failed, canceled, timeout)"
                  constraints:
                    nullable: false
              - column:
                  name: is_active
                  type: ${boolean.type}
                  remarks: "True only for currently running replacements, null for completed"
                  constraints:
                    nullable: true
              - column:
                  name: progress
                  type: float
                  remarks: "Progress from 0.0 to 1.0"
                  constraints:
                    nullable: true
              - column:
                  name: message
                  type: ${text.type}
                  remarks: "Human-readable message; may contain error info"
                  constraints:
                    nullable: true
              - column:
                  name: user_id
                  type: int
                  remarks: "User who initiated the replacement"
                  constraints:
                    nullable: true
              - column:
                  name: start_time
                  type: ${timestamp_type}
                  remarks: "When the replacement started"
                  defaultValueComputed: current_timestamp
                  constraints:
                    nullable: false
              - column:
                  name: end_time
                  type: ${timestamp_type}
                  remarks: "When the replacement completed (null if still running)"
                  constraints:
                    nullable: true

  - changeSet:
      id: v60.2026-03-06T12:00:01
      author: bcm
      comment: Enforce at most one active source replacement run cluster-wide
      changes:
        - addUniqueConstraint:
            tableName: source_replacement_run
            constraintName: idx_unique_active_source_replacement_run
            columnNames: is_active

  - changeSet:
      id: v60.2026-03-06T12:00:02
      author: bcm
      comment: Add index on source_replacement_run.user_id
      changes:
        - createIndex:
            tableName: source_replacement_run
            indexName: idx_source_replacement_run_user_id
            columns:
              - column:
                  name: user_id

  - changeSet:
      id: v60.2026-03-06T12:00:03
      author: bcm
      comment: Add foreign key on source_replacement_run(user_id)
      changes:
        - addForeignKeyConstraint:
            baseTableName: source_replacement_run
            baseColumnNames: user_id
            referencedTableName: core_user
            referencedColumnNames: id
            constraintName: fk_source_replacement_run_user_id

# >>>>>>>>>> DO NOT ADD NEW MIGRATIONS BELOW THIS LINE! ADD THEM ABOVE <<<<<<<<<<

########################################################################################################################
#
# ADVICE:
#
# 1) Think through some of these points when writing a migration, learn from our past mistakes:
#    - Do you really need a migration? Could the feature work without it? Prefer not to if possible.
#      Data in the wild can be vastly different from what you expect, and it's hard to get right.
#    - Make sure your migration is backward compatible: it might not be possible to add a constraint back
#      if you drop it in a migration.
#    - Postgres, MySQL and H2 have their differences. Make sure your migration works for all.
#    - Database encryption is a major issue:
#      - Fields like `metabase_database.details` or `setting.value` can be encrypted, so you need to decrypt them in
#        your migration. See #42617, #44048.
#      - Database could be partially encrypted, see https://www.notion.so/72575933ef2a446bafd16909e05a7387
#    - Custom migrations:
#      - Prefer SQL migrations when possible.
#      - Never use application code: it can change and *will* break your migration.
#      - Do not use Toucan models - refer table names directly.
#      - If it's a big change, consider using Quartz, see #42279
#      - More in `metabase.app_db.custom_migrations` namespace doc.
#    - Never delete a migration: users won't be able to downgrade. If you really need to, see #44908
#    - Migration id (`vXX.<date>`) must match its earliest released version:
#      - Do not backport `v51....` to version 50, Metabase will try to downgrade it.
#      - Instead, write a migration with an oldest target you plan to backport to in mind.
#
# 2) Migrations should go in the ###_update_migrations.yaml file for the target version.
#
# 3) Run mage lint-migrations to run core.spec checks against any changes you make here. Liquibase is pretty
#    forgiving and won't complain if you accidentally mix up things like deleteCascade and onDelete: CASCADE. CI runs
#    this check but it's nicer to know now instead of waiting for CI.
#
# 3) Migration IDs should follow the format
#
#    vMM.TIMESTAMP
#
#    Where
#
#    M         = major version
#    TIMESTAMP = the current timestamp with format `yyyy-MM-dd'T'HH:mm:ss`
#                To get this timestamp, evaluate this in your REPL: `(dev/migration-timestamp)`
#
#    E.g: You're adding a new migration for version 49, And it's 10:30:00AM on April 1, 2023 (UTC),
#    your migration id should be: `v49.2023-04-01T10:30:00`.
#
# PLEASE KEEP THIS MESSAGE AT THE BOTTOM OF THIS FILE!!!!! Add new migrations above the message.
#
########################################################################################################################