Documentation

Manage file indexes

InfluxDB 3 Enterprise lets you customize how your data is indexed to help optimize query performance for your specific workload, especially workloads that include single-series queries. Indexes help the InfluxDB query engine quickly identify the physical location of files that contain the queried data.

By default, InfluxDB indexes on the primary key—time and tag columns. However, if your schema includes tags that you don’t specifically use when querying, you can define a custom indexing strategy to only index on time and columns important to your query workload.

For example, if your schema includes the following columns:

  • country
  • state_province
  • county
  • city
  • postal_code

And in your query workload, you only query based on country, state or province, and city, you can create a custom file indexing strategy that only indexes on time and these specific columns. This makes your index more efficient and improves the performance of your single-series queries.

File indexes can use any string column, including both tags and fields.

Indexing life cycle

InfluxDB 3 Enterprise builds indexes as it compacts data. Compaction is the process that organizes and optimizes Parquet files in storage and occurs in multiple phases or generations. Generation 1 (gen1) data is un-compacted and is not indexed. Generation 2 (gen2) data and beyond is all indexed.


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.2

Key enhancements in InfluxDB 3.2 and the InfluxDB 3 Explorer UI is now generally available.

See the Blog Post

InfluxDB 3.2 is now available for both Core and Enterprise, bringing the general availability of InfluxDB 3 Explorer, a new UI that simplifies how you query, explore, and visualize data. On top of that, InfluxDB 3.2 includes a wide range of performance improvements, feature updates, and bug fixes including automated data retention and more.

For more information, check out: