edge-shard-query
An experimental binary that opens a ReadOnlyEdgeShard directly over object storage (S3/S3-compatible or GCS) — or over a running Qdrant peer's StorageRead gRPC service — and runs a single read request against it.
There is no Qdrant server in the loop for the object-storage backends. The tool reads segment files itself, through a local disk cache, so it is the fastest way to answer "what does the data in this bucket actually contain?" and to watch a leader's writes land.
Running it
cargo run -p edge-shard-query -- <CONNECTION FLAGS> <SUBCOMMAND> <SUBCOMMAND FLAGS>
Connection flags must come before the subcommand; request flags come after it. For repeated use, build once (cargo build -p edge-shard-query --release) and call target/release/edge-shard-query directly.
Logging is on at info by default; raise it with RUST_LOG=debug.
Choosing a backend
--backend selects where segments are read from. It defaults to aws.
| Backend | What it reads | Shard addressed by |
|---|---|---|
aws | AWS S3 or any S3-compatible store (MinIO, RustFS, LocalStack) | --bucket + --prefix |
gcs | Google Cloud Storage | `--buc… |