content/influxdb3/clustered/admin/tables/create.md
Use the influxctl table create command
to create a table in a specified database in your
{{< product-name omit=" Clustered" >}} cluster.
With {{< product-name >}}, 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.
If you haven't already, download and install the influxctl CLI.
Run the influxctl table create command and provide the following:
%Y-%m-%d)[!Note] {{< product-name >}} supports up to 7 total tags or tag buckets in the partition template.
{{% code-placeholders "(DATABASE|TABLE)_NAME" %}}
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
{{% /code-placeholders %}}
{{< product-name >}} 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.
[!Warning]
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 names in {{< product-name >}} must adhere to the following naming restrictions:
_), dash (-)_)[!Caution]
Underscore prefix reserved for system use
Names starting with an underscore (
_) may be reserved for InfluxDB system use. While {{< product-name >}} 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.