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

FlagDescriptionInput typeMaps to ?
-c--active-configConfig name to use for commandstringINFLUX_ACTIVE_CONFIG
--bucket-idBucket ID to map to
--configs-pathPath to the influx CLI configurations (default: ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
--dbInfluxDB v1 database to map from
--defaultSet DBRP mapping’s retention policy as default
-h--helpHelp for the create command
--hide-headersHide table headers (default: false)INFLUX_HIDE_HEADERS
--hostHTTP address of InfluxDBstringINFLUX_HOST
--jsonOutput data as JSON (default: false)INFLUX_OUTPUT_JSON
-o--orgOrganization name (mutually exclusive with --org-id)stringINFLUX_ORG
--org-idOrganization ID (mutually exclusive with --org)stringINFLUX_ORG_ID
--rpInfluxDB v1 retention policy to map from
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
-t--tokenAPI tokenstringINFLUX_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 powered by TSM