Assistants

FeatureQL includes built-in tools for inspecting, debugging, and exploring your features — all accessible from within the query language itself.

Inspecting queries with EXPLAIN

Prefix any query with EXPLAIN to see the generated SQL, output schema, and entity relationships without executing it:

EXPLAIN SELECT 1 AS FEATURE1, FEATURE1 + 1 AS FEATURE2;

This is the fastest way to check what SQL FeatureQL will produce for a given query. The query_sql field shows the CTE structure, query_outputs lists the result columns with their types, and entities shows any entity relationships discovered.

Inspecting features with DESCRIBE

DESCRIBE shows metadata about a specific feature — its function, parameters, dependencies, and type information:

CREATE TEMPORARY FEATURES AS SELECT 1 AS FEATURE1, FEATURE1 + 1 AS FEATURE2;
DESCRIBE FEATURE2;

Use this when you need to understand how a feature is defined, what it depends on, or what type it produces. It works with both temporary and persisted features.

Recreating features with SHOW CREATE

SHOW CREATE FEATURES returns the FeatureQL code needed to recreate one or more features. This is useful for understanding how features are stored internally and for exporting definitions.

For temporary features:

START TRANSACTION;
CREATE TEMPORARY FEATURES AS SELECT 1 AS FEATURE1, FEATURE1 + 1 AS FEATURE2;
SHOW CREATE FEATURES FEATURE1, FEATURE2;
COMMIT;

Notice that FeatureQL reorders features by dependency layer and may rewrite syntax — 1 becomes VALUE(1), for example. The semantics are preserved even when the surface syntax changes.

For persisted features, the output includes full namespace paths:

CREATE OR REPLACE FEATURES AS
SELECT
    1 AS FM.TUTORIALS.ASSISTANTS.FEATURE1,
    FM.TUTORIALS.ASSISTANTS.FEATURE1 + 1 AS FM.TUTORIALS.ASSISTANTS.FEATURE2
;

SHOW CREATE FEATURES FM.TUTORIALS.ASSISTANTS.FEATURE2;

Features are topologically ordered by their dependency graph, making the output self-contained — you can run it directly to recreate the features.

Cross-dialect SQL output

Specify a target dialect to see the actual SQL that would run in a specific backend:

SHOW CREATE FEATURES (LANGUAGE DUCKDB)
    FM.TUTORIALS.ASSISTANTS.FEATURE1,
    FM.TUTORIALS.ASSISTANTS.FEATURE2
;

Supported dialects: DUCKDB, TRINO, BIGQUERY, DATAFUSION. The output includes CTEs, stage comments, and dialect-specific syntax — useful for understanding how FeatureQL maps to your backend.

Exploring documentation

SHOW DOCS lets you search the built-in documentation without leaving the query environment:

SHOW DOCS (
    EXCLUDE (content),
    INCLUDE (LENGTH(name) as lname)
)
WHERE lname>30 and category = 'DOC_PAGE'
ORDER BY name ASC
LIMIT 5

Filter by category, search content with LIKE, and sort results to find relevant pages, code samples, and function references. Combined with SHOW FUNCTIONS and SHOW FUNCTION SIGNATURES (covered in Operators & Functions ), these tools make FeatureQL largely self-documenting.

Code samples

They represent end to end tests for capabilities. They use the SLT formalism to describe the test.

# name_of_the_test
query f1:I,f2:I,f3:V [rowsort]
SELECT
--
--
----
1   2   A

The line query represent the expected output of the query: column names and types.

Types in SLT queries are represented as:

• I: INTEGER
• D: DOUBLE or DECIMAL
• V: VARCHAR
• B: BOOLEAN
• T: TIMESTAMP or DATE
• J: JSON
• R: ROW
• A: ARRAY OF SCALARS
• Q: ARRAY OF ROWS