Reference · built on requestConnectorDatabases & warehouses

CockroachDB

Tables and row-level changefeeds from CockroachDB over the PostgreSQL wire protocol, delivered to Kafka, Pub/Sub, storage, or webhooks.

Request accessPricing ↗

About

CockroachDB is Cockroach Labs' distributed SQL database, offered as CockroachDB Cloud in Basic, Standard, and Advanced tiers, or self-hosted. It speaks version 3.0 of the PostgreSQL wire protocol on port 26257 and reports itself as PostgreSQL 18, so pgx, psycopg, node-postgres, and JDBC drivers connect with a postgresql:// string. Changefeeds, created with CREATE CHANGEFEED FOR TABLE ... INTO 'sink', emit each row change at least once, ordered per key by timestamp, to Kafka, Amazon MSK, Confluent Cloud, Google Cloud Pub/Sub, Azure Event Hubs, cloud storage, or a webhook-https:// endpoint. The Cloud API at https://cockroachlabs.cloud/api/v1 manages clusters and SQL users.

An operator on Fibric reads tables or subscribes a changefeed to its webhook, and proposes SQL row changes for your approval, each with a receipt and undo.

This is a reference listing. It documents what Fibric would read from CockroachDB and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Rows from tables the SQL user can SELECT, queried over pgwire with any PostgreSQL driver
  • Changefeed messages for a table at a webhook-https:// sink, in json, avro, csv, parquet, or protobuf format
  • Resolved timestamps emitted at the interval you set with the resolved option, so the reader knows a window is complete
  • Before-images of updated rows when the changefeed is created with the diff option
  • Changefeed job state from SHOW CHANGEFEED JOBS
  • Cluster, node, and SQL user records from the Cloud API, versioned by the Cc-Version header

Proposed actions

  • Target capability: propose an INSERT or UPDATE against a named table over pgwire, once, after approval
  • Target capability: propose CREATE CHANGEFEED for a table into your sink with format and initial_scan chosen in the proposal
  • Target capability: propose a SQL user change through the Cloud API, shown in full before it is sent

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Stream order events to the operator instead of scraping tables

    Create a changefeed on the orders table into a webhook-https:// sink with resolved timestamps, so the operator processes complete windows and acknowledges each batch.

    With Order Risk, Webhook Replay

  • Prove a changefeed is still flowing

    Read SHOW CHANGEFEED JOBS and the gap between the latest resolved timestamp and now, and flag a feed that stalls or errors.

    With Integration Health, Data Freshness

  • Ask questions across regions without moving data

    Query the tables directly over pgwire from the region nearest the reviewer and show the rows behind a figure.

    With Operations Analyst

Requirements

  • A CockroachDB cluster reachable on port 26257 with sslmode=verify-full and, for self-hosted or Advanced clusters, the CA certificate
  • The CHANGEFEED privilege on each target table, or the admin role, to create a changefeed
  • An HTTPS endpoint with a certificate for webhook sinks, since webhook-https:// does not accept plain HTTP
  • A Cloud API service account with a secret key for cluster and SQL user operations
Authentication
For SQL, client certificate and key authentication, password authentication over TLS with the cluster CA certificate, or JWT for SQL connections; for the Cloud API, a service account secret key sent as Authorization: Bearer.

Limits

  • Changefeeds deliver at least once; the same row change can arrive twice and the consumer must dedupe by key and timestamp
  • Ordering holds only for the first emit of each key by timestamp, not across keys or tables
  • Range types, XML functions, column-level privileges, foreign data wrappers, and session-scoped advisory locks are unsupported, so some PostgreSQL SQL needs changes
  • The Cloud API is rate-limited to 10 requests per second per user

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request CockroachDB ↗

Questions and answers

Can I use a PostgreSQL driver?
Yes. CockroachDB implements version 3.0 of the PostgreSQL wire protocol and sends the startup parameters drivers expect from PostgreSQL 18. The connection string is postgresql://user:password@host:26257/db?sslmode=verify-full. Some PostgreSQL features, such as range types and foreign data wrappers, are unsupported.
What does a changefeed guarantee?
Each emitted row change is delivered at least once, and the first emit of every event for the same key is ordered by timestamp. Add the resolved option to receive timestamps that mark a window as complete, and diff to include the previous row values.
Which sinks can a changefeed write to?
Kafka, Amazon MSK, Confluent Cloud, Google Cloud Pub/Sub, Azure Event Hubs, cloud storage, webhook, and Apache Pulsar in preview. Webhook sinks use the webhook-https:// prefix, require HTTPS, and batch messages according to webhook_sink_config.
Ask about CockroachDB

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with CockroachDB through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy