A source syntax such as SQL, PromQL, or MetricsQL.
The semantics of what a query requests, independent of the source language. Different query strings can express the same intent.
A set of queries considered together. It can describe a batch of queries or queries that recur while data arrives.
The common, exact representation of query intent. It contains no ASAP primitive or summary choice.
A logical plan representation that can contain ASAP primitives, alongside relational and time-series operations.
One legal Post-ASAP alternative for answering an intent. Planner preserves alternatives for downstream selection rather than committing to one.
Maintained state, exact or approximate, that can answer some query intent more efficiently than raw data. A sketch is one kind of approximate summary.
A concrete execution and deployment choice: runtime topology of data lifecycle stages, placement of computation, transmission, storage. Physical plans are owned by downstream systems.
A node of the physical DAG whose output is kept across evaluations (MatAtIngestion or MatAtQueryKeptAcrossEvaluations), with how long it is kept (retention_ms on the node). A MatAtQuery node is not a view: its output is discarded after one evaluation. Code: MaterializedView, PhysicalASAPDAG::materialized_views.
One timestamped value of a time series as it arrives, such as one Prometheus Remote Write sample. Raw data samples are the rows a time-series scan reads. Code names them with raw_data_sample, e.g. WeightDomain::RawDataSamplesOfMetric, raw_data_samples_of_metric.
The subset of input rows a sampling summary family, such as a reservoir, keeps as its state. Code names it SummarySample / summary_sample, e.g. FieldDataType::SummarySample(SamplingKind, SamplingParams). A summary sample is not a raw data sample, and the rows it is drawn from need not be raw data samples.