Documentation

Delete a custom file index

Use the influxdb3 delete file_index command to delete a custom file indexing strategy from a database or a table and revert to the default indexing strategy.

Provide the following:

  • Token (--token): (Required) Your admin token. You can also use the INFLUXDB3_AUTH_TOKEN environment variable to specify the token.
  • Database (-d, --database): (Required) The name of the database to apply remove the custom index from. You can also use the INFLUXDB3_DATABASE_NAME environment variable to specify the database.
  • Table (-t, --table): The name of the table to remove the custom index from. If no table is specified, the custom indexing strategy is removed from all tables in the specified database.
influxdb3 delete file_index \
  --host http://localhost:8585 \
  --database 
DATABASE
_NAME \
--table
TABLE
_NAME \

Replace the following placeholders with your values:

  • AUTH_TOKEN: your admin token
  • DATABASE_NAME: the name of the database to remove the custom file index from
  • TABLE_NAME: the name of the table to remove the custom file index from

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