Documentation

influx v1 dbrp create

The influx v1 dbrp create command creates a DBRP mapping with the InfluxDB 1.x compatibility API.

Usage

influx v1 dbrp create [flags]

Flags

Flag Description Input type Maps to ?
-c --active-config Config name to use for command string INFLUX_ACTIVE_CONFIG
--bucket-id Bucket ID to map to
--configs-path Path to the influx CLI configurations (default: ~/.influxdbv2/configs) string INFLUX_CONFIGS_PATH
--db InfluxDB v1 database to map from
--default Set DBRP mapping’s retention policy as default
-h --help Help for the create command
--hide-headers Hide table headers (default: false) INFLUX_HIDE_HEADERS
--host HTTP address of InfluxDB string INFLUX_HOST
--json Output data as JSON (default: false) INFLUX_OUTPUT_JSON
-o --org Organization name (mutually exclusive with --org-id) string INFLUX_ORG
--org-id Organization ID (mutually exclusive with --org) string INFLUX_ORG_ID
--rp InfluxDB v1 retention policy to map from
--skip-verify Skip TLS certificate verification INFLUX_SKIP_VERIFY
-t --token API token string INFLUX_TOKEN

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token
Create a DBRP mapping
influx v1 dbrp create \
  --bucket-id 12ab34cd56ef \
  --db example-db \
  --rp example-rp \
  --default

If a DBRP mapping already exists for the database name, the --default flag sets the new mapping as the default.


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud Serverless