Replication profiles¶

Navigate: Configure → Replication Profiles (/replication-profiles).

A replication profile tells Paridity which tool moves your data from a source system to a target system. That single fact is what turns a table-diff into a CDC-aware reconciliation: knowing the tool lets the platform read its state and refuse to compare a window replication hasn't finished delivering.

Without a profile, a mapping still works — but readiness short-circuits, CDC integration is forced to disabled, and latency/quiescence controls are unavailable. You are then comparing on trust rather than on evidence that the window is safe.

Which tools are usable today¶

The picker lists 22 tools. Be aware of what the badges mean, because most are not yet selectable.

Selectable now: Debezium, Airbyte, Fivetran, Oracle GoldenGate (Microservices REST 21c+, plus a Classic-architecture heartbeat-table mode), Qlik Talend Cloud (SaaS Data Integration — a distinct product from Qlik Replicate), Native / Direct Replication, Custom / Other.

Everything else shows "Future Release" and is disabled — including SAP SLT, SAP BODS, Qlik Replicate, Informatica PowerExchange CDC, IBM InfoSphere, Striim, SQL Server Transactional Replication, AWS DMS, Google Datastream, Azure Data Factory, Microsoft Fabric Mirroring, Kafka Connect and Fivetran HVR.

Fivetran HVR is a different product from Fivetran

Fivetran's managed SaaS connectors are supported. Fivetran HVR, the self-hosted high-volume replication product, is a separate entry in the picker and is not yet available.

If your stack uses one of the future-release tools, choose Custom / Other. The mapping works and comparison is fully accurate; what you lose is tool-aware readiness, so set max_lag_seconds and quiescence_seconds to match your pipeline's real behaviour. The UI warns you about exactly this when you pick Custom.

The legacy none value resolves automatically to Native / Direct.

Creating a profile¶

A profile is a route: one source system, one target system, one tool. The combination must be unique — creating a second profile for the same trio is rejected.

Field	Notes
Name	Optional but recommended, e.g. ECC FI/CO → Snowflake (SLT).
Business Domain	Required by the form.
Description	Optional.
Source System	Fixed after creation.
Target System	Fixed after creation. The source is excluded from the list.

Source, target and tool cannot be changed after creation. To re-route, create a new profile.

Debezium: replication lag (optional)¶

A Debezium profile's tool configuration has an optional Metrics endpoint: the Prometheus URL of the JMX exporter running on the Kafka Connect worker (for example http://kafka-connect:9404/metrics). When it is set, every readiness check reads the connector's streaming MilliSecondsBehindSource and the run's Replication tool line shows it as the tool's own lag. Leave it empty and Debezium lag stays unmeasured - shown as "did not report a lag figure", never as zero. Kafka Connect's own REST API does not carry a lag figure, so there is no other source for it.

The value must be an http:// or https:// URL; anything else is refused when you save.
The figure is the delay of the last change the connector processed. On a quiet source it keeps its last value until the next change arrives.
A connector that has not streamed a change since it started reports no figure yet (Debezium publishes -1 until then).
If the endpoint is down or slow (the read gives up after 2 seconds), the run records why and readiness carries on exactly as it would have.
The Kafka Connect credential is never sent to the metrics endpoint.

Debezium: sink connector (optional)¶

Connector name is the Debezium source connector, the one that captures changes into Kafka. A Kafka Connect sink connector usually applies those changes to the target, and readiness cannot see it unless you name it. Set the optional Sink connector name and readiness also checks that this sink connector is running: the tool's state reads as running only when both connectors are running with no failed task.

Leave it empty and only the source connector is checked, exactly as before.
When set, it must be a connector name; a blank value is refused when you save.
If the sink is paused, stopped or failed, the run's readiness record says the sink connector was the cause. Connector names are not written to the run's evidence - only which side it was and its state.
What a not-running connector does to a run depends on the mapping:
- Snapshot mappings (no watermark) are held - readiness status Replication not running - and re-checked on the normal readiness backoff, because a snapshot comparison has nothing else to show whether the target is up to date. This applies in advisory CDC mode too.
- Mappings with a watermark follow the mapping's CDC mode as before: advisory carries on with the watermark latency check, strict stops.
- A tool that cannot be reached at all (timeout, connection refused) is not a definite answer: advisory carries on and the run is marked degraded; strict stops.

Watermark defaults¶

These pre-populate new mappings created under the profile; every mapping can override them.

Field	Options
Default Watermark Strategy	`control_marker (preferred)`, `delta_version (CDC offset)`, `ingest_ts (load completion)`, `partition_max (ADLS/Hive)`, `timestamp (max field)`, `custom (last resort)`
Watermark Domain	`time_utc` or `sequence`

The form pre-selects what the chosen tool actually produces — Debezium defaults to delta_version in the sequence domain, Airbyte to ingest_ts in time_utc — and shows the recommendation inline.

See Watermarks and windows for what each strategy means.

Comparison defaults¶

These are inherited by every field under the profile unless a field overrides them. They exist to declare how your replication pipeline behaves, so Paridity canonicalizes both sides the same way.

Field	Purpose
Default Numeric Rounding Mode	How the pipeline rounds when decimal scale is reduced. Applies to DECIMAL/NUMERIC only. Unset behaves as half-away-from-zero.
Default Timestamp Rounding Mode	How the pipeline rounds when sub-second precision is reduced — e.g. a microsecond source loaded into `DATETIME2(3)`. Unset behaves as truncate.
Default Dual Compare Mode	How Qlik dual values (numeric + display text) are compared. Only affects QVD file datasets.

Selecting "None / inherit …" clears a saved value and returns the setting to inheriting. Picking the explicit equivalent (Half up …, Truncate (default), Automatic (default)) instead stores that concrete value.

Replicated tables¶

On an existing profile, Refresh asks the tool which tables it is actively replicating. Auto-configuration can then propose mappings only for tables the tool genuinely covers.

Not every tool supports this. When it doesn't, you get a clear message that live discovery isn't available for that tool and that the profile is otherwise fully functional — only automated listing is missing.

Associated mappings¶

A read-only list of mappings using this profile, each showing whether it is enabled. Useful before changing defaults.

Changing the business domain¶

The Business Domain can be changed on an existing profile. Because the domain controls who can see the profile, you can only move it to a domain you also have access to — an attempt to move it outside your scope is refused, and the change is written to the audit log.