Documentation

Create a table

Use the influxctl table create command to create a table in a specified database in your InfluxDB cluster.

With InfluxDB Clustered, tables and measurements are synonymous. Typically, tables are created automatically on write using the measurement name specified in line protocol written to InfluxDB. However, to apply a custom partition template to a table, you must manually create the table before you write any data to it.

  1. If you haven’t already, download and install the influxctl CLI.

  2. Run the influxctl table create command and provide the following:

    InfluxDB Clustered supports up to 7 total tags or tag buckets in the partition template.

influxctl table create \
  --template-tag tag1 \
  --template-tag tag2 \
  --template-tag-bucket tag3,100 \
  --template-tag-bucket tag4,300 \
  --template-timeformat '%Y-%m-%d' \
  
DATABASE_NAME
\
TABLE_NAME

Custom partitioning

InfluxDB Clustered lets you define a custom partitioning strategy for each table. A partition is a logical grouping of data stored in Apache Parquet format in the InfluxDB 3 storage engine. By default, data is partitioned by day, but, depending on your schema and workload, customizing the partitioning strategy can improve query performance.

Use the --template-tag, --template-tag-bucket, and --template-timeformat flags to define partition template parts used to generate partition keys for the table. If no template flags are provided, the table uses the partition template of the target database. For more information, see Manage data partitioning.

Partition templates can only be applied on create

You can only apply a partition template when creating a table. You can’t update a partition template on an existing table.

Table naming restrictions

Table names in InfluxDB Clustered must adhere to the following naming restrictions:

  • Allowed characters: Alphanumeric characters (a-z, A-Z, 0-9), underscore (_), dash (-)
  • Starting character: Should start with a letter or number and should not start with underscore (_)
  • Case sensitivity: Table names are case-sensitive
  • Quoting: Use double quotes when names contain special characters or whitespace

Underscore prefix reserved for system use

Names starting with an underscore (_) may be reserved for InfluxDB system use. While InfluxDB Clustered might not explicitly reject these names, using them risks conflicts with current or future system features and may result in unexpected behavior or data loss.


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