Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2709 ETL / Data Migration Service
  3. MXS-4437

Implement generic ODBC migration

    XMLWordPrintable

Details

    • Sub-Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 23.02.0
    • Core
    • None
    • MXS-SPRINT-166, MXS-SPRINT-167, MXS-SPRINT-168, MXS-SPRINT-169, MXS-SPRINT-170, MXS-SPRINT-171, MXS-SPRINT-172, MXS-SPRINT-173, MXS-SPRINT-174, MXS-SPRINT-175, MXS-SPRINT-176, MXS-SPRINT-177

    Description

      A "fallback" migration implementation for unknown source database types can be created by using the ODBC catalog functions. This allows all ODBC data sources to be used for ETL but the resulting SQL might require updates from the user to fully work. It'll still serve as a good starting point to which manual edits can be done.

      Attachments

        Activity

          People

            markus makela markus makela
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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