ETL / Data Migration Service
(MXS-2709)
|
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 23.02.0 |
| Type: | Sub-Task | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 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. |