View Source Rambla.Handlers.Clickhouse (Rambla v1.2.6)
Default handler for Clickhouse connections. For this handler to work properly, one must configure it with
config :rambla, :clickhouse,
connections: [
conn_1: "http://default:password@host-master-1:8123/database"
],
channels: [
chan_1: [connection: :conn_1]
]
# Then you can access the connection/channel via `Rambla.Handlers.Clickhouse` as
Rambla.Handlers.Clickhouse.publish(:chan_1, %{message: %{foo: 42}, table: :events, serializer: Jason})To install Clickhouse, visit https://clickhouse.com/docs/en/getting-started
CREATE TABLE events
(
source_id UInt32,
timestamp DateTime,
message String
)
ENGINE = MergeTree
PRIMARY KEY (source_id, timestamp)Summary
Functions
The list of child_spec returned
to be embedded into a supervision tree.
An interface to publish messages using the FSM pool.
The entry point: this would start a supervisor with all the pools and stuff
Functions
The list of child_spec returned
to be embedded into a supervision tree.
Known options:
connection_options— akeyword()or a function of arity one, which is to receive channel names and return connection options as a listcount— the number of workers in the poolchild_opts— the options to be passed to the worker’s spec (you won’t need those)
Example
Rambla.Handlers.Redis.children_specs(
connection_options: [exchange: "amq.direct"], count: 3)An interface to publish messages using the FSM pool.
The id is the specific to an implementation,
for Amqp it’d be the channel name, for instance.
The second parameter would be a payload, or, if the backend supports it,
the function of arity one, which would receive back the connection pid.
Example
Rambla.Handlers.Amqp.publish :channel_name, %{foo: :bar}@spec start_link([ Supervisor.option() | Supervisor.init_option() | {:connection_options, keyword() | (term() -> keyword())} | {:count, non_neg_integer()} ]) :: Supervisor.on_start()
The entry point: this would start a supervisor with all the pools and stuff