Summary

InfluxDB 3.12 builds on the major performance upgrade in 3.11, bringing 3x faster bulk imports, distributed compaction, per-database schema enforcement, and generally available role-based access control to InfluxDB 3 Enterprise, giving deployments more ways to scale and more control over how production data evolves and who can access it.

Time series deployments rarely grow the way they were planned. A single-node pilot becomes a multi-node fleet, an afternoon’s worth of test data becomes weeks of backfill that has to land before anyone can query it, and three teams end up writing to a database built for one.

InfluxDB 3.11 delivered a higher-performance foundation for complex time series workloads, with significant performance improvements for single-series queries, schemas that could go wide and sparse without breaking, and a much more predictable resource profile.

For InfluxDB 3 Enterprise, 3.12 builds on that foundation with more ways to scale operations around those workloads. Bulk imports make better use of available CPU, compaction can now scale across nodes, and schema enforcement gives teams more control over shared production datasets.

The common thread is simple: as the workload grows, more of the system can grow with it.

Bulk import, now 3x faster

Historical data isn’t useful until it’s queryable. When you’re migrating to InfluxDB or backfilling months of history, import speed decides how soon that data sits alongside your live data, whether that’s by lunch or next week.

InfluxDB 3.12 makes bulk import from Parquet roughly three times faster. Imports now run in parallel, so they scale with the hardware you give them. In testing, import time fell by 64-70 percent across workloads.

Imports are also easier to lock down. Bulk import no longer requires an admin token. It now authorizes against write permission on the target database, so the credential running a backfill only needs access to the data it’s loading.

Distributed compaction, now in beta

Compaction keeps queries fast by organizing newly written data into efficient files in the background. At high ingest volumes, though, that background work can become the bottleneck: compaction falls behind, and the only fix is a bigger machine.

InfluxDB 3.12 removes that ceiling. With distributed compaction, now in beta, compaction becomes something you can scale horizontally. When compaction needs more capacity, add nodes running in compact mode, and the coordinating node spreads jobs across them. If a compact node drops out mid-job, the work is simply reassigned in the next scheduling cycle.

Distributed compaction is off by default, so existing deployments behave exactly as they do today. When you’re ready to scale past a single compactor, you can turn it on.

Schema enforcement, per database

Schema-on-write is one of the things that makes InfluxDB easy to start with: send data, and the schema takes shape around it. But in a production database shared by several applications, that flexibility cuts both ways. A typo in a field name or an unexpected column from one service quietly becomes part of the schema, and every team querying that database has to work around it.

InfluxDB 3.12 lets you lock the schema down where it matters. Define the schema when you create a database, and writes that introduce undefined columns are rejected instead of changing the schema. Bad data gets caught at write time, before it reaches dashboards, queries, or downstream consumers.

Schema-on-write remains the default, so you can enforce schemas on the databases that production depends on and keep exploratory databases as flexible as ever.

More control in the Explorer UI

The Explorer UI has a set of updates to keep pace with the teams using it.

InfluxDB 3.12 makes role-based access control generally available in InfluxDB 3 Enterprise, so teams can manage access by user and role instead of tracking individual tokens. Users can sign in with a token, a password, or SSO, and using Explorer, admins can manage users and their roles from the same place they query.

Explorer also adds six visualization types: area, single stat, gauge, pie, scatter, and ranking. Explain in SQL shows what a query is doing, which makes it easier to check before you rely on it. New deployments also start with Explorer preconfigured, so the first query doesn’t wait on connection parameters.

InfluxDB 3.12

Other improvements in InfluxDB 3 Enterprise

  • The Processing Engine can now run as a separate process, so teams can deploy custom Python plugins without worrying about them affecting database stability.
  • InfluxDB 3 Core and Enterprise now run on Apache DataFusion 52, picking up another round of query performance improvements across joins, CASE expressions, and query planning.

Upgrading a multi-node deployment?

InfluxDB 3.12 has new requirements for node roles and upgrade order. Review the release notes before upgrading.

Get started with InfluxDB 3.12

With 3.12, more of InfluxDB scales with your workloads. Compaction can scale horizontally, imports get faster as you add cores, and production schemas no longer have to evolve by accident.

Download the latest version of InfluxDB 3 Enterprise, pull the newest Docker image, or check out the docs (Core, Enterprise) to get started.