Behaviour defining the InfluxDB client contract.

All library modules use this behaviour — never a concrete implementation directly. The implementation is selected via application configuration:

# config/config.exs (default: production HTTP client)
config :influx_elixir, :client, InfluxElixir.Client.HTTP

# config/test.exs (test: LocalClient)
config :influx_elixir, :client, InfluxElixir.Client.Local

Implementations

• InfluxElixir.Client.HTTP — production Finch-based client
• InfluxElixir.Client.Local — in-memory ETS-backed test client

Connection Lifecycle

Each implementation defines how connections are created and destroyed:

• init_connection/1 — converts raw keyword config into the implementation's native connection type. Called by ConnectionSupervisor during startup.

  • Client.HTTP returns the keyword config as-is
  • Client.Local creates an ETS table and returns a conn map

• shutdown_connection/1 — cleans up resources when a connection is removed. Called by InfluxElixir.remove_connection/1.

  • Client.HTTP is a no-op (Finch pool has its own supervisor)
  • Client.Local deletes the ETS table

Canonical Connection Config Schema

Every implementation must accept the same keys from init_connection/1 so a config is a drop-in replacement across implementations. See InfluxElixir.Config for the canonical schema. Keys consumed by both implementations:

• :database — connection-level default database name. When the caller does not pass database: in opts, this value is used.
• :databases — list of database names. Client.Local pre-creates each; Client.HTTP defaults :database to the first item when :database is not set.
• :profile — Client.Local only; ignored by Client.HTTP.

Implementations must not silently ignore the singular :database key.