Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-6772

For selected tables, keep data in Exasol when it is deleted in MariaDB

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 25.10.3
    • 26.10.0
    • exasol-cdc
    • None
    • MXS-SPRINT-276, MXS-SPRINT-277
    • Hide
      The new Exasol CDC setting `odbc_insert_only_tables` lists tables whose data
      is kept in Exasol when it is deleted in MariaDB. Inserts and updates to these
      tables are replicated, but deletes are not, and neither are `TRUNCATE TABLE`,
      `DROP TABLE` or `ALTER TABLE ... DROP COLUMN`. See
      [odbc_insert_only_tables]({maxscale}/reference/maxscale-routers/maxscale-exasol-cdc#odbc_insert_only_tables)
      for more information.
      Show
      The new Exasol CDC setting `odbc_insert_only_tables` lists tables whose data is kept in Exasol when it is deleted in MariaDB. Inserts and updates to these tables are replicated, but deletes are not, and neither are `TRUNCATE TABLE`, `DROP TABLE` or `ALTER TABLE ... DROP COLUMN`. See [odbc_insert_only_tables]({maxscale}/reference/maxscale-routers/maxscale-exasol-cdc#odbc_insert_only_tables) for more information.

    Description

      As a user I want a minimal, config-driven prototype that lets MaxScale's CDC apply INSERT operations for a specified set of tables, while leaving all other tables in normal full replication mode.
      The purpose is to prove the filtering mechanics work operationally before investing in orchestration & control-table & status signaling.

      Scope

      • Add two new config parameters to the Exasol CDC router:
      • odbc_operations_filter — some combination of insert, update, delete or mode? Replication vs Insert
      • odbc_operations_filter_tables — comma-delimited list of db.tables the filter applies to
      • maybe only 1 config needed? odbc_insert_only_tables — comma-delimited list of db.tables that only get inserts
      • Tables not listed in odbc_operations_filter_tables but are in odbc_include_tables continue in normal replication mode (all operations), unaffected.
      • Config changes require a MaxScale service restart

      Attachments

        Issue Links

          Activity

            People

              nantti Niclas Antti
              allen.herrera Allen Herrera
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 4d
                  4d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 3.25d Time Not Required
                  3.25d

                  Git Integration

                    Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.