mirror of https://github.com/hanzo-ds/rs.git synced 2026-10-30 20:49:56 +00:00

Files

T

History

zeekay 86788566d1 datastore: rebrand the Rust client and speak the Datastore wire protocol

Cut from the upstream v0.13.3 release tag (not HEAD) so this is a pure
rename with no behaviour change. v0.13.3 is what our consumers already
resolve to: insights/rust's Cargo.lock pins clickhouse 0.13.3 and its
manifest already declares `datastore` at 0.13.x.

The load-bearing change is the HTTP auth header rename. The Datastore
server reads only X-Datastore-User / X-Datastore-Key; the upstream names
return `401 Code: 194 Authentication failed`. Every un-renamed HTTP
client is therefore unable to authenticate at all — this is a
correctness fix, not branding.

- crate `clickhouse` -> `datastore`, `clickhouse-derive` -> `datastore-derive`;
  versions preserved exactly (0.13.3 / 0.2.0).
- derive macro emits `datastore::Row` in lockstep, so downstream
  `#[derive(Row)]` keeps resolving.
- User-Agent reports `datastore-rs/{version}`.
- test-harness env vars CLICKHOUSE_* -> DATASTORE_*; compose uses
  ghcr.io/hanzoai/datastore with /etc/datastore-server config paths.
- doc links point at docs.hanzo.ai/datastore.
- `publish = false`: the `datastore` name on crates.io belongs to an
  unrelated crate, so consume this by git tag, never by version range.

CHANGELOG is truncated to a fork notice rather than find-replaced —
rewriting upstream release history would manufacture changes Datastore
never shipped. References to upstream issues keep their numbers.

2026-07-26 11:30:32 -07:00

common.rs

datastore: rebrand the Rust client and speak the Datastore wire protocol

2026-07-26 11:30:32 -07:00

insert.rs

datastore: rebrand the Rust client and speak the Datastore wire protocol

2026-07-26 11:30:32 -07:00

README.md

datastore: rebrand the Rust client and speak the Datastore wire protocol

2026-07-26 11:30:32 -07:00

select_numbers.rs

datastore: rebrand the Rust client and speak the Datastore wire protocol

2026-07-26 11:30:32 -07:00

select.rs

datastore: rebrand the Rust client and speak the Datastore wire protocol

2026-07-26 11:30:32 -07:00

README.md

Benchmarks

All cases are run with cargo bench --bench <case>.

With a mocked server

These benchmarks are run against a mocked server, which is a simple HTTP server that responds with a fixed response. This is useful to measure the overhead of the client itself:

select checks throughput of Client::query().
insert checks throughput of Client::insert() and Client::inserter() (if the inserter features is enabled).

How to collect perf data

The crate's code runs on the thread with the name testee:

cargo bench --bench <name> &
perf record -p `ps -AT | grep testee | awk '{print $2}'` --call-graph dwarf,65528 --freq 5000 -g -- sleep 5
perf script > perf.script

Then upload the perf.script file to Firefox Profiler.

With a running Datastore server

These benchmarks are run against a real Datastore server, so it must be started:

docker compose up -d
cargo bench --bench <case>

Cases:

select_numbers measures time of running a big SELECT query to the system.numbers_mt table.

How to collect perf data

cargo bench --bench <name> &
perf record -p `ps -AT | grep <name> | awk '{print $2}'` --call-graph dwarf,65528 --freq 5000 -g -- sleep 5
perf script > perf.script

Then upload the perf.script file to Firefox Profiler.