Database and retention policy mapping
The InfluxDB 1.x data model includes databases and retention policies. InfluxDB Cloud replaces databases and retention policies with buckets. To support InfluxDB 1.x query and write patterns in InfluxDB Cloud, databases and retention policies are mapped to buckets using the database and retention policy (DBRP) mapping service.
The DBRP mapping service uses the database and retention policy specified in 1.x compatibility API requests to route operations to a bucket.
To query data in InfluxQL that was written using the api/v2/write API,
you must manually create a DBRP mapping to map a bucket to a database and retention policy.
For more information, see Create DBRP mappings.
Default retention policies
A database can have multiple retention policies with one set as default.
If no retention policy is specified in a query or write request, InfluxDB uses
the default retention policy for the specified database.
Use the influx CLI or the InfluxDB API to set a retention policy as the
default retention policy for a database.
When writing data
When writing data using the
/write compatibility endpoint,
the DBRP mapping service checks for a bucket mapped to the database and retention policy:
-
If a mapped bucket is found, data is written to the bucket.
-
If an unmapped bucket with a name matching:
database/retention policyexists, a DBRP mapping is added to the bucket, and data is written to the bucket.databaseexists (without a specified retention policy), the default database retention policy is used, a DBRP mapping is added to the bucket, and data is written to the bucket.
When querying data
When querying data from InfluxDB Cloud
using the /query compatibility endpoint,
the DBRP mapping service checks for the specified database and retention policy
(if no retention policy is specified, the database’s default retention policy is used):
- If a mapped bucket exists, data is queried from the mapped bucket.
- If no mapped bucket exists, InfluxDB returns an error. See how to Create DBRP mappings.
For more information on the DBRP mapping API, see the /api/v2/dbrps endpoint documentation.
A DBRP combination can only be mapped to a single bucket
Each unique DBRP combination can only be mapped to a single bucket. If you map a DBRP combination that is already mapped to another bucket, it will overwrite the existing DBRP mapping.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.