Skip to main content
Use the @bijection/connectors/debezium entrypoint to declare Debezium PostgreSQL resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Database

cdc: cdc

The following example matches configuration standard.

Configuration: standard

Case: debezium/database/cdc/standard. Connection and resource configuration are declared by this exact case. Credential kind: postgres. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: lines
Collection: orders
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

debezium.database.cdc({contract: cdc}) consumes the module generated by bijection debezium capture --connection /private/cdc.json --output cdc.json. Capture writes cdc.json and cdc.ts. The installation’s postgresConnection points to the ordinary private PostgreSQL credential JSON. Capture reads the catalog in a read-only serializable transaction while holding schema locks; the application does not repeat schemas or keys. Native admission independently compares type OIDs, modifiers, nullability, primary keys and the complete scope. This profile pins PostgreSQL 16.14, Debezium 3.7.0.Final and Kafka Connect 4.1.0. It requires pgoutput, a complete initial snapshot, transaction metadata, single-partition topics from offset zero, embedded JSON schemas, precise decimals and REPLICA IDENTITY FULL. Install io.bijection.debezium.SourceOffsets from the pipelines repository’s src/debezium/ package. Filtering, custom keys, other transforms and unsafe producer overrides are refused. Topic access must include DescribeConfigs: effective cleanup.policy must be delete, retention.ms at least seven days (or unlimited), and retention.bytes unlimited. Offset continuity is checked independently, including after retention changes. The customer operates Kafka Connect, Kafka and the PostgreSQL replication slot. The responding Connect worker must report the pinned version and PostgreSQL plugin; this is an observation of that worker, not a cluster-wide attestation. Operators must deploy the admitted artifacts uniformly across eligible workers. The actual broker cluster ID must match both Connect and the installed binding. The PostgreSQL private credential adds debezium.configuration_digest, broker_cluster_id, broker, broker_credential (shared Kafka TLS/SASL JSON), connect_endpoint, optional Connect authentication and private CA, connector, topic_prefix and notification_topic. SQL catalog access is required. Physical bindings and secrets stay outside the generated application module. Raw Kafka records enter bounded ordinary acquisition custody before decoding. Raw acquisition and interpretation have independent cursors; a semantic refusal continues raw capture within the source budget. The archive pins input across publication and crashes. Stable provider identities reject conflicting duplicate content at different Kafka offsets. The earliest unresolved transaction gets priority over unrelated lookahead. BEGIN/END counts, table counts and global order must agree before tables, required views and the checkpoint publish. Tombstones do not prove deletion; complete delete envelopes do. integration source-status reports raw, sealed and published progress, their timestamps, waiting topic, bounds and stage pauses. integration postgres-control accepts pause_acquisition, resume_acquisition, pause_publication and resume_publication with the observed native revision. Acquisition pause does not pause interpretation of retained input. Publication pause is checked again in the final publication transaction. These are independent of Connect pause. To retry a decoder failure after deploying a repair, pause acquisition, inspect the exact debezium_archive.replay_plan digest, then use control replay --plan with that digest and revision. It retries the retained unpublished prefix, preserving its generation, schema and published predecessor. It cannot roll back publication, invent missing bytes or admit a changed schema. Schema, identity and continuity changes require an explicit new contract and rebaseline. This is a bounded recovery archive, not indefinite Kafka history. Capacity exhaustion stops acquisition visibly without advancing publication. Empty broker polls do not improve source freshness. Complete zero-row source transactions can establish quiet progress. Hosted qualification remains separate from source checks and in-memory tests. Connect mutations require a deployed --source and the usual deployment selector. The native external-call owner commits intent before a PUT, uses an exclusive hold, and reconciles unknown outcomes with GET only. The private PostgreSQL credential must declare debezium.control_authority as {"kind":"observe"} or {"kind":"exclusive","grants":["configure","pause","resume","stop"]}. Grant only needed actions. Configuration control repairs the installation’s captured contract; initial enrollment and changed private bindings use a checked capture and the normal connection owner. debezium operation-status --operation inspects retained control custody without starting a pending send. Task status remains the evidence of asynchronous connector completion. Replay also validates the current SQL catalog before resuming retained interpretation.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.