Expand description
Qdrant REST protocol surface: the closed response IR, telemetry, the strict OpenAPI response parser, collection-schema reading, and response normalization.
Nothing here performs I/O. qql-runtime uses it as its REST response
boundary and re-exports it to keep the executor API stable; the WASM host
consumes the same parser and normalizer directly, so both hosts cannot
drift on response shapes. The crate sits above qql-plan: plans carry
the typed request, this crate turns backend envelopes back into typed
ExecData.
Re-exports§
pub use normalize::normalize_planned;pub use response::*;pub use rest::*;pub use schema::*;pub use telemetry::*;
Modules§
- normalize
- Pure
BackendResponse→ExecResponseshaping shared by all hosts. Pure response normalization: typedBackendResponse→ExecResponse. - response
- The closed response IR:
ExecDatafamily, scores, telemetry envelope. - rest
- Strict OpenAPI REST response parsing, one shape per operation. Strict REST response parsing: one OpenAPI shape per operation.
- schema
- Collection metadata types and the REST schema reader. Transport-neutral QQL backend model.
- telemetry
- Server telemetry and client phase timings.
Phase-1 telemetry: client-side phase timings plus server
time/usageextraction.