Expand description
SQL grammar and engine-dimensioned feature matrix for Krishiv.
Provides a machine-readable inventory of which SQL dialect features are
supported, and — crucially — in which of the three execution engines:
batch (DataFusion planner + Krishiv extensions), streaming (continuous
window compiler), and incremental (IVM / krishiv-delta). A single feature is
frequently “supported in batch, partial in streaming, n/a in incremental”,
so each FeatureEntry carries a per-engine FeatureStatus rather than
one global status — otherwise “measured coverage” silently means batch
coverage (Phase 60).
The public SQL reference page is generated from this matrix
(generate_reference_markdown), never hand-written, and a CI drift guard
(see coverage.rs) asserts the checked-in page matches and that every
non-n/a engine cell is backed by an executable coverage case.
Structs§
- Feature
Entry - A single entry in the Krishiv SQL feature matrix, dimensioned per engine.
Enums§
- Engine
- The three Krishiv execution engines a feature can be dimensioned across.
- Feature
Status - Support status for a single SQL feature in one engine.
- Placement
- An execution surface a feature can be reached from. A
supportedengine cell alone cannot say where the feature runs (audit §9b): several real, tested streaming operators are reachable only from the embeddedStreamingDataFrame/process API, while the distributedstream:loopruntime executes onlyWindowExecutionSpecshapes (windows, window-join, CEP) and the SQL front door compiles a further subset.
Constants§
- EMBEDDED_
ONLY_ OPERATORS - The embedded-API-only streaming operator tier (audit §9b). These have no
SQL spelling, so they carry no
FeatureEntryrow; they are published on the generated reference page so the placement restriction is stated somewhere a user will read it.
Functions§
- feature_
matrix - Return the complete Krishiv SQL feature matrix.
- features_
by_ status - Return entries whose batch status equals
status. (Batch is the primary column; useFeatureEntry::status_forfor the other engines.) - features_
for_ category - Return only entries matching
category(case-insensitive prefix match). - generate_
honesty_ markdown - Render the “Krishiv SQL vs Spark SQL” dialect honesty / migration page from the matrix + the documented per-feature semantic differences. Generated, never hand-written: what maps 1:1, what differs semantically, what is absent.
- generate_
reference_ markdown - Render the public “Krishiv SQL feature matrix” reference page from the matrix. This is the single source of truth; the checked-in markdown is regenerated from here and drift-guarded in CI.