Last cache creation will be done via a new REST API.

Details

• Method: POST
• Endpoint: /api/v3/configure/last_cache
• Request Body

  {
    "db" : "foo",
    "table" : "table1",
    "name" : "last_values_table1",
    "key_columns" : ["col1", "col2"],
    "value_columns": ["col3", "col4"],
    "count" : 3,
    "ttl_seconds": 600,
  }

The API should have the last cache added to the catalog, as well as have it set up in the internal last cache (#25093).

Defaults

• name: <table_name>_[key_columns,]_lastcache the name can be defaulted based on the table name plus the key columns used. There shouldn't be two last caches on the same table with the same key columns.
• key_columns: the series key, or the lexicographically ordered tag set on the table
• count: 1
• ttl_seconds: 4 hours (in seconds)