Documentation

influxdb3 import upload

The influxdb3 import upload command uploads one or more Parquet files into an existing InfluxDB 3 Enterprise database and table. Each file becomes a separate import job. Imported data is written to your object storage and becomes queryable after the compactor processes it.

Usage

influxdb3 import upload [OPTIONS] [PATH]

Arguments

ArgumentDescription
[PATH]Path to a Parquet file or a directory. If a directory, all *.parquet files are processed recursively and one import job is created per file.

Options

OptionDescriptionDefaultEnvironment variable
--host <HOST_URL>Host URL of the InfluxDB 3 Enterprise serverhttp://127.0.0.1:8181INFLUXDB3_HOST_URL
--token <AUTH_TOKEN>Authentication tokenINFLUXDB3_AUTH_TOKEN
--database <DATABASE>Target database nameINFLUXDB3_DATABASE_NAME
--table <TABLE>Target table name
--column <COLUMN>Map a Parquet column to an InfluxDB type: <column>:<type>. Supported types: i64, u64, f64, bool, string, time, tag. Can be specified multiple times. Unmapped columns default to field values.
--tls-ca <CA_CERT>Path to a custom TLS certificate authorityINFLUXDB3_TLS_CA
--tls-no-verifyDisable TLS certificate verification (not recommended in production)INFLUXDB3_TLS_NO_VERIFY
-h--helpPrint help information
--help-allPrint detailed help information

Column type mapping

The --column option maps Parquet columns to InfluxDB data types. Specify the option multiple times to map multiple columns. Unmapped columns default to field values.

TypeDescription
i64Signed 64-bit integer field
u64Unsigned 64-bit integer field
f6464-bit float field
boolBoolean field
stringString field
timeTimestamp column
tagTag column

Examples

In the examples below, replace the following:

  • DATABASE_NAME: the name of the target database
  • TABLE_NAME: the name of the target table
  • AUTH_TOKEN: your authentication token

Upload a single Parquet file

influxdb3 import upload \
  --host http://localhost:8181 \
  --token 
AUTH_TOKEN
\
--database
DATABASE_NAME
\
--table
TABLE_NAME
\
/path/to/data.parquet

Upload all Parquet files in a directory

influxdb3 import upload \
  --host http://localhost:8181 \
  --token 
AUTH_TOKEN
\
--database
DATABASE_NAME
\
--table
TABLE_NAME
\
/path/to/parquet-directory/

Upload with column type mapping

influxdb3 import upload \
  --host http://localhost:8181 \
  --token 
AUTH_TOKEN
\
--database
DATABASE_NAME
\
--table
TABLE_NAME
\
--column timestamp:time \ --column host:tag \ --column cpu_usage:f64 \ /path/to/metrics.parquet

Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 2026, 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