Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API for creation of last_caches #25096

Closed
Tracked by #25091
hiltontj opened this issue Jun 25, 2024 · 0 comments · Fixed by #25147
Closed
Tracked by #25091

API for creation of last_caches #25096

hiltontj opened this issue Jun 25, 2024 · 0 comments · Fixed by #25147
Assignees
Labels

Comments

@hiltontj
Copy link
Contributor

hiltontj commented Jun 25, 2024

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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant