Feature releases by surface.
One place per query surface to see what the engine supports today, what is in preview, and what changed. The support lists are read from the engine rather than written by hand, and the date they were read is recorded below.
How to read this page.
Two sources feed it, and they answer different questions. They are kept apart on every section below.
- Current state comes from the engine's own capability endpoint, which publishes a support list per capability family. Several of those lists are generated from the same check the engine runs when it accepts or refuses a configuration, and the engine's tests hold others to what the query surface actually does, failing in both directions: a variant that is advertised but refused fails the build, and so does a variant left on the roadmap that the engine in fact serves. The endpoint carries no dates.
- History comes from the changelog, which is the only dated record. Each item below links to its entry. Where the changelog has no dated entry for something, it is not listed rather than given an approximate date.
The three columns in each table use the engine's own definitions:
supported is implemented
and generally available; preview is shipped but
deliberately narrow and not yet generally available;
roadmap is
accepted by the schema but refused by the engine at configuration time, so it is not usable
today. A dash means the arm is empty.
Support lists were read from the engine's capability endpoint on 2026-09-06. The endpoint publishes 25 capability families; 21 of them describe a query surface and are listed below. The rest describe the deployment - the instruction set of the host CPU, the write topology, the replication mode, and row-level concurrency control - and are not properties of any one surface, so they are not shown here.
Elasticsearch.
A search API shaped like the Elasticsearch REST and Query DSL surface, answered by the same engine as everything else. Elasticsearch overview .
The engine's capability endpoint publishes no family for Elasticsearch, so there is no support list here that the engine's tests hold to account. Rather than write one by hand, this section carries only the dated history below and points you at the reference pages, which document the surface as it is built.
What changed, and when.
The changelog records no dated entry for Elasticsearch. Until one exists there is no date to quote, so none is given here. The elasticsearch overview documents what the surface does today.
SQL.
The /sql endpoint and the wire protocols that ride it. This is the surface the capability endpoint covers in most detail. SQL reference .
| Capability family | Supported today | In preview | On the roadmap |
|---|---|---|---|
| Joins sql_joins | — |
|
|
| Common table expressions sql_cte | — |
|
|
| Window functions sql_window_functions | — |
|
|
| Constraints sql_constraint_kinds |
| — |
|
| INSERT ... ON CONFLICT sql_insert_on_conflict | — |
| — |
| Materialized view refresh sql_materialized_view_refresh_modes |
|
|
|
| Isolation levels sql_isolation_levels |
| — |
|
| Triggers sql_trigger_kinds |
| — |
|
| Stored procedure languages sql_procedure_languages | — |
|
|
| User-defined function languages sql_udf_languages | — |
|
|
| PostgreSQL wire compatibility postgres_wire | — |
|
|
| MySQL wire compatibility mysql_wire_dialect | — |
|
|
| TDS wire compatibility mssql_tds_dialect | — |
|
|
What changed, and when.
- v1.2 2026-06-08
Materialized views with on-demand refresh. Foreign-key and CHECK constraints, with NoAction, Restrict and SetNull as the on-delete actions. The join cap moved from 5 tables to 32.
- v1.0 2026-05-02
GROUP BY with COUNT, SUM, AVG, MIN and MAX; INNER and LEFT, RIGHT and FULL OUTER joins; HAVING filters.
Graph.
Relationship traversal and graph embeddings. The capability endpoint publishes families for the embedding side only. Graph reference .
| Capability family | Supported today | In preview | On the roadmap |
|---|---|---|---|
| Embedding algorithms graph_embedding_algos |
| — | — |
| Embedding aggregators graph_embedding_aggregators |
|
|
|
What changed, and when.
- v1.2 2026-06-08
GraphSAGE attribute-aware node embeddings, with Mean, MaxPool and LSTM aggregators. Cypher v3 closed CALL subqueries, nested FOREACH, list comprehensions, MERGE, DELETE, CREATE relation and multi-hop undirected matches.
- v1.0 2026-05-02
Forward and reverse one-hop neighbours, breadth-first search to a configurable maximum depth, path reachability, and weighted shortest path by Dijkstra with a caller-supplied weight function.
Vector.
Approximate nearest-neighbour search: which index kinds exist, how vectors are compressed, and where an index lives. Vector reference .
| Capability family | Supported today | In preview | On the roadmap |
|---|---|---|---|
| Index kinds index_kinds |
| — | — |
| Quantization quantization |
| — | — |
| Index residency index_residency |
| — |
|
What changed, and when.
- v1.2 2026-06-08
IVF and IVF-PQ indexes landed end to end. Binary quantization and PQ quantization attach to HNSW or IVF as separate index kinds, so the recall and memory trade-off is chosen per collection.
- v1.0 2026-05-02
HNSW with cosine, dot and L2 metrics, filtered topk by metadata equality, and f32 SIMD distance kernels.
Natural language.
The /ask endpoint, which compiles a natural-language question into a query plan. Ask reference .
The engine's capability endpoint publishes no family for Natural language, so there is no support list here that the engine's tests hold to account. Rather than write one by hand, this section carries only the dated history below and points you at the reference pages, which document the surface as it is built.
What changed, and when.
- v0.10 2026-04-22
Every /ask call compiles in the same region as the tenant's instance, with credentials scoped per instance and a scope locked to a single model identifier. Repeated calls over the same catalog pay the cached-read rate on the schema prompt.
- v0.7 2026-02-12
The plan cache spills to disk, so a cold start reloads hot plans instead of recompiling them.
- v0.5 2025-12-18
The natural-language to query-plan compiler shipped in the first release, alongside HTTP ingress and the row-keyed store.
Full-text.
Ranked text search. The capability endpoint publishes the per-field analysis knobs: tokenizer, lemmatizer and geospatial index kind. Full-text reference .
| Capability family | Supported today | In preview | On the roadmap |
|---|---|---|---|
| Tokenizers fts_tokenizer_kinds |
| — | — |
| Lemmatizers fts_lemmatizers |
| — | — |
| Geospatial index kinds geo_index_kinds |
| — |
|
What changed, and when.
- v1.2 2026-06-08
Lemmatization for nine languages - English, Spanish, French, German, Italian, Portuguese, Russian, Dutch and Swedish - reducing inflected forms to a dictionary-backed lemma. ICU and geo tokenizers shipped alongside.
- v1.0 2026-05-02
BM25 ranking at the Lucene defaults, phrase queries by position-list intersection, the UAX #29 Unicode tokenizer, and Snowball stemming for 18 languages.
What this page does not cover.
The gaps are worth stating, because an absence here means an absence in the sources, not a judgement about the surface.
- Graph traversal and graph algorithms. The capability endpoint publishes families for graph embeddings only. Traversal, path finding and the algorithm set are documented on the graph reference, and the dated entries above cover what the changelog recorded for them.
- Query-side full-text features. The endpoint publishes the per-field analysis knobs - tokenizer, lemmatizer, geospatial index kind - not the query operators. Those are on the full-text reference.
- Per-family detail. Each family carries engineering notes and stated limitations that this page does not reproduce, because a paraphrase of them here is exactly the hand-maintained text this page exists to replace. Read the capability endpoint on your own instance for the full text.
- Anything undated. A capability can appear as supported above with no entry under "what changed" - that means the changelog has no dated record of it, not that it landed recently.
PostgreSQL, MySQL, Elasticsearch and other product names are trademarks of their respective owners. Naming them here describes wire-protocol and API compatibility only, and implies no affiliation with or endorsement by those projects.