Capabilities for YugabyteDB

This section lists the Capabilities of Fivetran HVR when using 'YugabyteDB'. For more information about the pre-requisites, access privileges, and other configuration requirements, see PostrgeSQL Requirements.

Capture

HVR supports the following capabilities on YugabyteDB:

• Capture changes from location (YugabyteDB version 2024.1).
• Log-based capture (capture from DBMS logging system) (YugabyteDB version 2024.1).
• Access to logs using SQL interface (YugabyteDB version 2024.1).
• Log-based capture of tables with LOB column (YugabyteDB version 2024.1).
• Multiple log-based capture jobs can capture from same database (YugabyteDB version 2024.1).
• Log-based capture checkpointing using location property Capture_Checkpoint_Frequency (YugabyteDB version 2024.1).

HVR does not support the following capabilities on YugabyteDB:

• Capture from Archive log files only.
• Log-based capture of tables without a primary key.
• Direct access to logs on a file system.
• Log-based capture from hidden rowid/RRN column (ColumnProperties with parameter CaptureFromRowId).
• Rewind log-based capture to specific time (hvractivate option -i).
• Online refresh using accurate LSN/SCN.
• Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions.
• Log-based capture of truncate table statements.
• Capture from tables with basic compression.
• Read archives from an alternative directory (location property Archive_Log_Path on the capture location).
• Trigger-based capture (location property Capture_Method=DB_TRIGGER on the capture location).

Repository Database

HVR does not support Repository database on YugabyteDB.

Integrate

HVR supports the following capabilities on YugabyteDB:

• Integrate changes into location (YugabyteDB version 2024.1).
• Burst integration (Integrate with parameter Method=BURST) (YugabyteDB version 2024.1).
• Integrate with parameter BurstCommitFrequency (YugabyteDB version 2024.1).
• Continuous integration (Integrate with parameter Method=CONTINUOUS) (YugabyteDB version 2024.1).
• Tables without a key and without TableProperties with NoDuplicateRows for continuous integration (YugabyteDB version 2024.1).
• Continuous integrate with parameter OnErrorSaveFailed (YugabyteDB version 2024.1).
• ColumnProperties with parameter SoftDelete (YugabyteDB version 2024.1).
• Creation and update of HVR state tables (YugabyteDB version 2024.1).

HVR does not support the following capabilities on YugabyteDB:

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

Bi-directional Replication

HVR supports the following capabilities on YugabyteDB:

• Detection of changes made by HVR in a bidirectional channel to prevent loop-back (YugabyteDB version 2024.1).
• CollisionDetect with parameter TimestampColumn (YugabyteDB version 2024.1).

HVR does not support the following capabilities on YugabyteDB:

• CollisionDetect with Log-based Capture (without parameter TimestampColumn).

Refresh and Compare

HVR supports the following capabilities on YugabyteDB:

• hvrrefresh or hvrcompare from source location (YugabyteDB version 2024.1).
• hvrrefresh into target location (YugabyteDB version 2024.1).
• Isolated table hvrrefresh (option -i) into target location (YugabyteDB version 2024.1).
• Row-wise hvrrefresh into target location (option -g) (YugabyteDB version 2024.1).

Other Capabilities

HVR supports the following capabilities on YugabyteDB:

• Call database procedure dbproc during replication jobs (AgentPlugin with parameter DbProc) (YugabyteDB version 2024.1).
• International table and column names where DBMS is not configured with UTF-8 encoding (YugabyteDB version 2024.1).
• Always treat DBMS table names and column names as case sensitive, even if not configured (equivalent to location property Case_Sensitive_Names always set to TRUE) (YugabyteDB version 2024.1).
• Always treat DBMS schema names case sensitive (YugabyteDB version 2024.1).

HVR does not support the following capabilities on YugabyteDB:

• Use distribution key for parallelizing changes within a table (ColumnProperties with parameter DistributionKey).
• Lossless binary float datatypes. No data loss when transporting float values (because base 2 fractions are never converted to base 10). The values for these datatypes, when selected back from the database, might be slightly different from the ones that were inserted. This leads to Compare differences..
• Distinguish and support capture from 'materialized views'.