Documentation

SQL cache functions

The InfluxDB 3 Core SQL implementation supports the following functions that return data from InfluxDB 3 Core caches.

distinct_cache

Returns data from an InfluxDB 3 Core distinct value cache.

distinct_cache(table_name, cache_name)

Arguments

  • table_name: Name of the table associated with the distinct value cache (formatted as a string literal).
  • cache_name: Name of the distinct value cache to query (formatted as a string literal).

View distinct_cache query example

last_cache

Returns data from an InfluxDB 3 Core last value cache.

last_cache(table_name, cache_name)

Arguments

  • table_name: Name of the table associated with the last value cache (formatted as a string literal).
  • cache_name: Name of the last value cache to query (formatted as a string literal).

View last_cache query example


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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