Creates a new cache for a specific table in a catalog. Caching copies data from an external data source into the internal Peaka BigTable store for faster query performance.
The cache can be configured in three modes:
incrementalCacheSchedule to periodically sync only the changes (inserts, updates, deletes) since the last sync.fullRefreshCacheSchedule and incrementalCacheSchedule. Full refresh drops and rebuilds the entire cached table periodically, while incremental updates run more frequently between full refreshes.After creation, the initial sync is triggered automatically based on the provided schedules. If only an incremental schedule is given, an incremental sync starts immediately. If a full refresh schedule is given, a full refresh starts immediately.
The schedule expression uses ISO-8601 duration format (e.g. PT6H = every 6 hours, PT15M = every 15 minutes, P1D = every day).


Use the Authorization header with the value 'Bearer
The unique identifier of the project that owns the data source
Cache creation request specifying the target table and optional sync schedules
This class represents a request to cache data. It contains the catalog ID, schema name, table name, and schedule of the cache request.
The ID of the catalog for the cache request.
The name of the schema for the cache request.
The name of the table for the cache request.
This class represents a schedule for a materialized query.
This class represents a schedule for a materialized query.
Cache created successfully. Returns the created cache configuration including its generated ID and schedules.
The ID of the cache.
The ID of the catalog for the cache request.
The name of the schema for the cache request.
The name of the table for the cache request.
This class represents a schedule for a materialized query.
This class represents a schedule for a materialized query.
The ID of the project for the cache request.