Documentation

Delete a Distinct Value Cache

Use the influxdb3 delete distinct_cache command to delete a Distinct Value Cache (DVC). Provide the following:

  • Database (-d, --database): (Required) The name of the database that the DVC 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 token.
  • Table (-t, --table): (Required) The name of the table that the DVC you want to delete is associated with.
  • Cache name: The name of the DVC to delete.
influxdb3 delete distinct_cache \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--table
TABLE_NAME
\
DVC_NAME

Replace the following:

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

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


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2