Configuration

AshClickhouse is configured in two places: the Repo (connection) and the resource (clickhouse DSL block).

Repo configuration

Defined in config/config.exs under your OTP app and Repo module:

config :my_app, MyApp.Repo,
  url: "http://localhost:8123",
  username: "default",
  password: "",
  database: "my_app_dev",
  pool_size: 10,
  pool_timeout: 30_000,
  ping_retry: 30_000

Repo API

The use AshClickhouse.Repo macro provides these functions:

• MyApp.Repo.config/0 — full repo config
• MyApp.Repo.database/0 — configured database
• MyApp.Repo.connection/0 — connection struct
• MyApp.Repo.query/3 / query!/3 — run raw SQL
• MyApp.Repo.insert_rows/4 — batch insert
• MyApp.Repo.ping/0 — true/false readiness check
• MyApp.Repo.create_database/1 / drop_database/1

config/0 and query/3 / query!/3 are defoverridable, so you can override them in your own Repo module if needed.

Application-wide configuration

A few behaviours are controlled via config :ash_clickhouse:

# config/config.exs
config :ash_clickhouse, :raise_on_untranslatable_filter, false

The resource → repo resolution is cached in an ETS table for the life of the VM. Test suites that redefine resources or repo config between tests can clear it with AshClickhouse.DataLayer.clear_repo_cache!/0.

Resource configuration

See Resources for the full clickhouse DSL options. The most important ones for configuration are:

• repo — which Repo the resource uses
• database — overrides the repo's default database
• engine, order_by, partition_by, primary_key, settings — table DDL
• base_filter — applied to every query (e.g. soft-delete scoping)
• default_context — merged into every query/changeset
• migrate — whether the resource participates in migrations

Connection options

The connection wrapper (AshClickhouse.Connection) accepts:

The default response format is JSONCompactEachRow.