Documentation

Delete a Last Value Cache

Use the influxdb3 delete last_cache command to delete a Last Value Cache (LVC). Provide the following:

  • Database (-d, --database): (Required) The name of the database that the LVC you want to delete is associated with. You can also use the INFLUXDB3_DATABASE_NAME environment variable to specify the database.
  • Token (--token): (Required) Your InfluxDB 3 Enterprise admin authentication token. You can also use the INFLUXDB3_AUTH_TOKEN environment variable to specify the database.
  • Table (-t, --table): (Required) The name of the table that the LVC you want to delete is associated with.
  • Cache name: The name of the LVC to delete.
influxdb3 delete last_cache \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--table
TABLE_NAME
\
LVC_NAME

Use the HTTP API

To use the HTTP API to delete a Last Value Cache, send a DELETE request to the /api/v3/configure/last_cache endpoint with query parameters.

DELETE /api/v3/configure/last_cache
curl -X DELETE "https://localhost:8181/api/v3/configure/last_cache?db=
DATABASE_NAME
&table=
TABLE_NAME
&name=
LVC_NAME
"
\
--header "Authorization: Bearer
AUTH_TOKEN
"

Example

curl -X DELETE "https://localhost:8181/api/v3/configure/last_cache?db=example-db&table=home&name=homeLastCache" \
  --header "Authorization: Bearer 00xoXX0xXXx0000XxxxXx0Xx0xx0"

Response codes:

  • 200 : Success. The last cache has been deleted.
  • 400 : Bad request.
  • 401 : Unauthorized.
  • 404 : Cache not found.

Replace the following:

  • DATABASE_NAME: the name of the database that the LVC you want to delete is associated with
  • AUTH_TOKEN: your InfluxDB 3 Enterprise admin authentication token
  • TABLE_NAME: the name of the table that the LVC you want to delete is associated with
  • LVC: the name of the LVC to delete

This is a destructive action that cannot be undone. Once deleted, any queries against the deleted LVC will return an error.


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Read more

New in InfluxDB 3.4

Key enhancements in InfluxDB 3.4 and the InfluxDB 3 Explorer 1.2.

See the Blog Post

InfluxDB 3.4 is now available for both Core and Enterprise, which introduces offline token generation for use in automated deployments and configurable license type selection that lets you bypass the interactive license prompt. InfluxDB 3 Explorer 1.2 is also available, which includes InfluxDB cache management and other new features.

For more information, check out: