Summary
A timeseries lake you can ask questions of.
The lake stops being something you write ingest scripts against: list what is there, read the schema, run the query and write back through one connection.
What it is
A SQL front door to a GigAPI cluster. Queries go through GigAPI's HTTP API and come back as NDJSON, and the same connection lists databases and tables, reads schemas, writes line-protocol data and checks the server is up.
What you get
- SELECT queries run against a named database on your cluster
- The databases on the cluster, and the tables inside one of them
- A table's schema, so a query can be written without guessing column names
- New points written in InfluxDB Line Protocol format
- A health check, for telling a dead cluster from an empty result
Requirements
Uv, and the connection details for your GigAPI cluster set as environment variables in the client config. There is a public demo instance if you want to try it before pointing it at your own.
Setup effort
Build from source — clone the repository and build it, then point your client at the binary