Skip to main content
Use the @bijection/connectors/couchbase entrypoint to declare Couchbase 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.

Collection keyspace

watermark: SQL++ watermark

The following example matches configuration standard.

Configuration: standard

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

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Bind the Query service origin (url, for example https://host:18093) on the connection and the SQL++ keyspace path (keyspace, for example `shop`.`sales`.`orders`) on the resource. Authenticate with Basic (couchbase.credential(name)), as a Couchbase RBAC user with query select on the keyspace.
  • Mechanism. SQL++ through POST /query/service, not DCP: DCP is a binary protocol with no client in this workspace. Each page selects META(d).id, TOSTRING(META(d).cas) and the document where the watermark is >= $1 and < $2, ordered by the watermark then META(d).id, with scan_consistency: request_plus.
  • Watermark. A top-level field every writer sets on every mutation, as toISOString() UTC text, covered by a GSI index. The host keeps the largest value a page carried; the inclusive bound re-reads it, deduplicated by CAS. A full page sharing one watermark cannot advance and fails visibly.
  • Why not CAS as the watermark. CAS is a hybrid logical clock per vBucket: not monotonic across nodes, failover-promoted replicas or XDCR, beyond exact JSON doubles, and not fixed-width text. It is the record version only.
  • Settle window. $2 is now minus settleMs (default 5 s), declared as the observation lag.
  • Deletions. Not observed: removed and expired documents leave the result set silently, and a document without the watermark is never read.
  • Read-only. The Query service takes no request precondition (no CAS or If-Match), and a SQL++ UPDATE ... WHERE META(d).cas = $cas reports its verdict in body fields that HTTP 200 also carries for timeouts, so no write could be declared conditional with an exact refusal. CAS-conditioned writes need the Data service (for example through Capella’s Data API), which is not built.
Not established: no request has reached Couchbase; the exact TOSTRING rendering of a 64-bit CAS is unverified.

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.