You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Metadata caches can be created via the following API:
POST /api/v3/configure/meta_cache
with body parameters:
db: database the cache is configured on
table: table the cache is configured on
name: (optional) name of the cache, must be unique within the db/table, will be generated if not provided
columns: (optional) list of ordered columns to construct the cache
max_age: (optional) values that have not been seen for this amount of time will be evicted from the cache
max_cardinality: (optional) the max number of unique value combinations to hold in the cache
The API should respond with a structure representing the created cache. This API should be idempotent, so duplicate calls to create a cache will not result in duplicate caches being created, but only a single cache. The last cache create API behaves similar.
The columns, if not provided in the request, will be selected as the tag set in lexicographical order, or the series key, of the table. Only string columns, i.e., tags or string fields, are allowed for the time being - specifying another column type is an error.
The max_cardinality will default to 100,000 if not specified.
The text was updated successfully, but these errors were encountered:
Metadata caches can be created via the following API:
with body parameters:
db
: database the cache is configured ontable
: table the cache is configured onname
: (optional) name of the cache, must be unique within the db/table, will be generated if not providedcolumns
: (optional) list of ordered columns to construct the cachemax_age
: (optional) values that have not been seen for this amount of time will be evicted from the cachemax_cardinality
: (optional) the max number of unique value combinations to hold in the cacheThe API should respond with a structure representing the created cache. This API should be idempotent, so duplicate calls to create a cache will not result in duplicate caches being created, but only a single cache. The last cache create API behaves similar.
The
columns
, if not provided in the request, will be selected as the tag set in lexicographical order, or the series key, of the table. Only string columns, i.e., tags or string fields, are allowed for the time being - specifying another column type is an error.The
max_cardinality
will default to 100,000 if not specified.The text was updated successfully, but these errors were encountered: