Capabilities for MariaDB

From HVR
Jump to: navigation, search

This section describes the capabilities supported by HVR on MariaDB. For more information about the requirements, access privileges, and other features of HVR when using Aurora MySQL for replication, see Requirements for MySQL and MariaDB.

Capture

HVR supports the following capabilities on MariaDB:

  • Capture changes from location (MariaDB version 10.0 and above, since HVR 5.3.1/13)
  • Log-based capture (capture from DBMS logging system) (MariaDB version 10.0 and above)
  • Log-based capture of tables without a primary key (MariaDB version 10.0 and above)
  • Direct access to logs on a file system (MariaDB version 10.0 and above)
  • Access to logs using SQL interface (MariaDB version 10.0 and above)
  • Log-based capture with /LogReadMethod param (MariaDB version 10.0 and above)
  • Log-based capture of tables with LOB column (MariaDB version 10.0 and above)
  • Rewind log-based capture to specific time (hvrinit option -i) (MariaDB version 10.0 and above, since HVR 5.3.1/15)
  • Online refresh using accurate LSN/SCN (MariaDB version 10.0 and above)
  • Log-based capture of truncate table statements (MariaDB version 10.0 and above, since HVR 5.3.1/21)
  • Multiple log-based capture jobs can capture from same database (MariaDB version 10.0 and above)
  • Capture from tables with any compression (MariaDB version 10.0 and above)


HVR does not support the following capabilities on MariaDB:

  • Log-based capture from hidden rowid column (ColumnProperties /CaptureFromRowId)
  • Rewind log-based capture to the beginning of currently active oldest transaction (MariaDB version 10.0 and above)
  • Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions (MariaDB version 10.0 and above)
  • Log-based capture checkpointing (action Capture /CheckpointingFrequency) (MariaDB version 10.0 and above)
  • hvrlogrelease to preserve journal/archives
  • Read archives from an alternative directory (Capture /ArchiveLogPath)
  • Trigger-based capture (action Capture /TriggerBased) (MariaDB version 10.0 and above)


HVR Hub

HVR supports Hub database (MariaDB version 10.0 and above)


Integrate

HVR supports the following capabilities on MariaDB:

  • Integrate changes into location (MariaDB version 10.0 and above)
  • Integrate with /Burst (MariaDB version 10.0 and above)
  • Integrate with /BurstCommitFrequency (MariaDB version 10.0 and above)
  • Continuous integration (Integrate without /Burst) (MariaDB version 10.0 and above)
  • Action TableProperties with /DuplicateRows for continuous integration (MariaDB version 10.0 and above)
  • Continuous integrate with /OnErrorSaveFailed (without /Burst) (MariaDB version 10.0 and above)
  • Action Transform /SoftDelete (MariaDB version 10.0 and above)
  • Bulk load requires a staging area (LocationProperties /StagingDirectoryHvr) (MariaDB version 10.0 and above)
  • Creation and update of HVR state tables


HVR does not support the following capabilities on MariaDB:

  • Disable/enable database triggers during integrate (/NoTriggerFiring)
  • Integrate with /DbProc


Bi-directional Replication

HVR supports the following capabilities on MariaDB:

  • Detection of changes made by HVR in a bidirectional channel to prevent loop-back (MariaDB version 10.0 and above, since HVR 5.3.1/13)
  • Collision Detect with /TimestampColumn (MariaDB version 10.0 and above, since HVR 5.3.1/13)


HVR does not support the following capabilities on MariaDB:


Refresh and Compare

HVR supports the following capabilities on MariaDB:


Other Capabilities

HVR supports the following capabilities on MariaDB:

  • Treat DBMS table names and columns case sensitive (action LocationProperties /CaseSensitiveNames)


HVR does not support the following capabilities on MariaDB:

  • Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey)
  • International table and column names where DBMS is not configured with UTF-8 encoding
  • Lossless binary float datatypes. No dataloss when transporting float values (because base 2 fractions are never converted to base 10)