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

Measurement

timeRange: SQL time range

The following example matches configuration standard.

Configuration: standard

Case: influxdb/measurement/timeRange/standard. Connection and resource configuration are declared by this exact case. Credential kind: influxdb. 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 server origin (url) on the connection and the database (database) on the resource. Authenticate with an InfluxDB 3 token as a bearer (influxdb.credential(name)).
  • Mechanism. InfluxDB 3 Core and Enterprise SQL through POST /api/v3/query_sql with format: "json". InfluxDB 2’s Flux answers annotated CSV, which no host codec decodes; Cloud Serverless and Dedicated serve SQL over Arrow Flight only, and their InfluxQL rows are positional and untyped.
  • Identity of a point. The compound of every declared tag and the point time; points missing a declared tag are not read. Writing the same series and time again replaces its fields.
  • Time range. time >= $since AND time < now() - INTERVAL '<settleMs>', ordered by time and tags, with time rendered as fixed-width nanosecond UTC text. The server holds back the settle window (default one minute), which is the declared observation lag. The host keeps the largest rendered time a page carried; the inclusive bound re-reads it.
  • Late writes. Point time is the writer’s timestamp. A point backfilled behind the derived maximum, or an overwrite of a point already read, is not observed. The version is the point time, so a re-read boundary point whose fields changed is deduplicated.
  • Deletions. Not observed.
Not established: no request has reached InfluxDB; to_char rendering, params binding and the bare-array response root are taken from documentation only.

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.