Using Materialized Views
Materialized views cache the results of a query and can speed up query processing, especially when replicating a query with heavily aggregated data. Once the query results are cached, materialized views must be manually updated and the manual query updates make take as long to perform as the original query.
Materialized view data is stored internally in either query engine memory or in dedicated external data connector storage. When it is initially loaded, it is stored in query engine memory and no target source ID (
targetSourceId) or field mappings (
targetFieldMappings) are provided. However, when the materialized view is recalled, its data is stored in external data connector storage and both the
targetFieldMappings are provided. You can use the
targetSourceId in some of the following cURL commands for the
Support for materialized views is performed using the REST API endpoint
/api/materialized-views, as described below.
|Returns a list of all materialized view mappings.|
|Creates a new materialized view mapping.|
|Updates a specific materialized view mapping.|
|Patches (partially updates) a specific materialized view mapping.|
|Deletes a specific materialized view mapping.|
For complete information about Zoomdata's API, see Composer REST API Overview.
Please sign in to leave a comment.