Documentation

Shortcode test page

InfluxDB 3 Core InfluxDB 3 Core core localhost:8181 Home sensor sample data 5 3.8.3

GET https://localhost:8181/api/v2/query
VISIBLE_IN_CORE [token](/influxdb3/core/admin/tokens/) [token](/influxdb3/core/admin/tokens/)

When working with the InfluxDB 3 Core SQL implementation a bucket is equivalent to a database, a measurement is equivalent to a table, and time, fields, and tags are structured as columns.

InfluxDB v1 to InfluxDB 3 data model

InfluxQL was designed around the InfluxDB v1 data model, but can still be used to query data from InfluxDB 3 Core. When using the InfluxDB 3 Core InfluxQL implementation, the data model is different in the following ways:

  • an InfluxDB v1 database and retention policy combination is combined into a single InfluxDB 3 database entity.
  • an InfluxDB v1 measurement is equivalent to an InfluxDB 3 table.

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On April 7, 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