A valid request URL is required to generate request examples{
"results": {
"tables": [
{
"columns": [
{
"description": "<string>",
"label": "<string>",
"type": "string",
"reference": "<string>"
}
],
"description": "<string>",
"label": "<string>",
"reference": "<string>"
}
],
"sourceType": "semanticLayer"
},
"status": "ok"
}{
"error": {
"name": "<string>",
"statusCode": 123,
"data": "<unknown>",
"message": "<string>"
},
"status": "error"
}Scan query source schema
Scans the schema of one query source into the standard shape: tables with columns of . For the semantic layer, tables are explores and columns are field ids; for warehouse SQL, tables come from the warehouse catalog resolved for your credentials, like the SQL runner; the duckdb source has no schema of its own — its tables are the references given to each query.
A valid request URL is required to generate request examples{
"results": {
"tables": [
{
"columns": [
{
"description": "<string>",
"label": "<string>",
"type": "string",
"reference": "<string>"
}
],
"description": "<string>",
"label": "<string>",
"reference": "<string>"
}
],
"sourceType": "semanticLayer"
},
"status": "ok"
}{
"error": {
"name": "<string>",
"statusCode": 123,
"data": "<unknown>",
"message": "<string>"
},
"status": "error"
}Path Parameters
Discriminator for every query source a project can execute queries against. A query source is anything that can scan a schema and run a query returning the standard table format (ResultColumns + rows behind a queryUuid): the project warehouse, the semantic layer, the DuckDB compose engine, and — later — CSV uploads, HTTP APIs, Google Sheets, etc.
Deliberately NOT WarehouseTypes: sources are not warehouses, they plug in above the warehouse client layer.
semanticLayer, sql, duckdb Was this page helpful?