influxdb3 create distinct_cache

The influxdb3 create distinct_cache command creates a new distinct value cache for a specific table and column set in your InfluxDB 3 Core instance.

Use this command to configure a cache that tracks unique values in specified columns. You must provide the database, token, table, and columns. Optionally, you can specify a name for the cache.

Usage

influxdb3 create distinct_cache [OPTIONS] \
  --database <DATABASE_NAME> \
  --token <AUTH_TOKEN>
  --table <TABLE> \
  --columns <COLUMNS> \
  [CACHE_NAME]

Arguments

• CACHE_NAME: (Optional) A name to assign to the cache. If omitted, the CLI generates a name automatically.

Options

Option environment variables

You can use the following environment variables to set command options:

Prerequisites

Before creating a distinct value cache, make sure you:

1. Create a database

2. Create a table that includes the columns you want to cache

3. Have a valid authentication token

Examples

Before running the following commands, replace the placeholder values with your own:

• DATABASE_NAME: The database name
• TABLE_NAME: The name of the table to cache values from
• CACHE_NAME: The name of the distinct value cache to create
• COLUMN_NAME: The column to cache distinct values from

You can also set environment variables (such as INFLUXDB3_AUTH_TOKEN) instead of passing options inline.

Create a distinct cache for one column

Track unique values from a single column. This setup is useful for testing or simple use cases.

influxdb3 create distinct_cache \
  --database 
DATABASE_NAME
 \
  --table 
TABLE_NAME
 \
  --column 
COLUMN_NAME
 \
  
CACHE_NAME

Create a hierarchical cache with constraints

Create a distinct value cache for multiple columns. The following example tracks unique combinations of room and sensor_id, and sets limits on the number of entries and their maximum age.

influxdb3 create distinct_cache \
  --database my_test_db \
  --table my_sensor_table \
  --columns room,sensor_id \
  --max-cardinality 1000 \
  --max-age 30d \
  my_sensor_distinct_cache

Common pitfalls

• --column is not valid. Use --columns.
• Tokens must be included explicitly unless set via INFLUXDB3_AUTH_TOKEN
• Table and column names must already exist or be recognized by the engine