usage: cox lake [-h] {sync,query,doctor} ...
The Iceberg lake: sync the run store and traces into it, query it with SQL, and check it. Needs the optional extra `lake`.
positional arguments:
{sync,query,doctor}
sync append new run-store rows and register new trace files;
--dry-run writes nothing
query run DuckDB SQL over the lake tables (runs, phases, ...)
and print the rows
doctor check the lake: catalog, namespace, warehouse and each
table; exits 1 on a failed check
options:
-h, --help show this help message and exit
examples:
cox lake sync
cox lake sync --dry-run --json
cox lake query "SELECT count(*) AS n FROM runs"
cox lake doctor
sync
usage: cox lake sync [-h] [--runs-dir RUNS_DIR] [--profile PROFILE]
[--dry-run] [--json]
options:
-h, --help show this help message and exit
--runs-dir RUNS_DIR
--profile PROFILE the routing profile naming the provider profile
(default: ~/.config/agent-tools/profile.yaml or
$AGENT_TOOLS_PROFILE)
--dry-run report what would be synced; create and write nothing
--json
query
usage: cox lake query [-h] [--runs-dir RUNS_DIR] [--profile PROFILE] [--json]
sql
positional arguments:
sql the SQL to run; a lake table is named by its bare name,
such as runs
options:
-h, --help show this help message and exit
--runs-dir RUNS_DIR
--profile PROFILE the routing profile naming the provider profile
(default: ~/.config/agent-tools/profile.yaml or
$AGENT_TOOLS_PROFILE)
--json
doctor
usage: cox lake doctor [-h] [--runs-dir RUNS_DIR] [--profile PROFILE] [--json]
options:
-h, --help show this help message and exit
--runs-dir RUNS_DIR
--profile PROFILE the routing profile naming the provider profile
(default: ~/.config/agent-tools/profile.yaml or
$AGENT_TOOLS_PROFILE)
--json