Materialized Views API (Experimental)
Note: Materialized view functionality is disabled by default. To enable, contact technical support for assistance. The Materialized Views API is deprecated and will be removed in a future release.
Materialized views allow you to use pre-aggregated query results, stored in some external storage, to speed up query processing in certain scenarios, especially when processing a query with heavily aggregated data.
Important: Pre-aggregated data is not managed by Composer, so it should be maintained manually and kept up to date by the owner of the data.
Important: This is an experimental feature.
API support for materialized views is performed using the REST API endpoint /api/materialized-views
, as described below.
Endpoint | Method | Description |
---|---|---|
|
GET |
Returns a list of all materialized view mappings. Optionally, include the |
|
POST |
Creates a new materialized view mapping. |
|
PUT |
Updates a specific materialized view mapping. |
|
PATCH |
Patches (partially updates) a specific materialized view mapping. |
|
DELETE |
Deletes a specific materialized view mapping. |
|
GET |
Returns information about all the fields and metrics in a data source. |
API documentation is provided with your Composer installation at this link: https://<composer-URL>/composer/swagger-ui.html
.
Here is a sample of the general object structure for materialized views:
"name": "string", "description": "string", "enabled": true, "definition": { ... }, "storageSettings": { "targetStorage": { ... }, "fieldMappings": [ ... ] } }
Each object is described in the following table.
Object | Specifies |
---|---|
|
The name of the materialized view definition. |
|
The description of the materialized view definition. |
|
Whether or not the definition is enabled. A value of |
|
The query that this materialized view should match. |
|
Where the data for the query results are stored. |
|
The connection and the specific table or collection of data. |
|
The mapping between the fields used in the definition and the columns or fields in the data identified by the Every field returned by the You can skip fields in the target table if they are not used in the query results (for example, redundant metrics). |
Comments
0 comments
Please sign in to leave a comment.