Repository navigation
docs(influxdb3): fix database naming limits for Core, Enterprise, and Cloud - #7934
Merged
Merged
Conversation
Contributor
Vale Style Check Results
Warnings (3)
✅ Check passed |
Contributor
🔗 Link Check Results — Link Check Bot✅ All links are valid
|
| Source File | URL | Issue |
|---|---|---|
content/influxdb3/cloud-dedicated/reference/naming-restrictions/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/cloud/admin/databases/create/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/clustered/reference/naming-restrictions/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/core/admin/databases/create/_index.md |
file:///home/runner/work/docs-v2/docs-v2/public/influxdb3/core/api/v3 | File not found. Check if file exists and path is correct: File not found. Check … |
content/influxdb3/core/admin/databases/create/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/core/reference/naming-restrictions/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/enterprise/admin/databases/create/_index.md |
file:///home/runner/work/docs-v2/docs-v2/public/influxdb3/enterprise/api/v3 | File not found. Check if file exists and path is correct: File not found. Check … |
content/influxdb3/enterprise/admin/databases/create/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/enterprise/reference/naming-restrictions/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
Full details: workflow run summary and artifact. Last updated: 2026-10-29 13:59:28 UTC
ritwika314
added
product:v3-monolith
sanderson
requested changes
Oct 27, 2026
sanderson
left a comment
sanderson
left a comment
Collaborator
There was a problem hiding this comment.
Two minor comment changes.
Comment on lines
+43
to
+44
| sensor.data # Contains period | ||
| app@server # Contains special character |
Collaborator
There was a problem hiding this comment.
Suggested change
| sensor.data # Contains period | |
| app@server # Contains special character | |
| sensor.data # Contains a period | |
| app@server # Contains a special character |
Collaborator
Author
There was a problem hiding this comment.
Applied in 3621daa — also updated the same two comments in the Dedicated/Clustered variant of the example. (automated follow-up)
ritwika314
force-pushed
the
ritwika/db-naming-limits
branch
from
October 29, 2026 12:25
3621daa to
d4998f3
Compare
… Cloud Database names in InfluxDB 3 Core, Enterprise, and Cloud allow up to 511 ASCII characters (not 64), start with an ASCII letter or number, and allow at most one forward slash as a database/retention policy separator (not first or last). Gate the 64-character rule in the shared naming-restrictions page to products that use the iox engine (Cloud Dedicated, Clustered). Source: validate_db_name in the Enterprise (July 2026 checkout) and Core http.rs; iox namespace_name.rs for the 64-character products. Co-Authored-By: Claude
Core and Enterprise reject a leading underscore, so drop "not recommended" there and keep each product's examples in a single block. Co-Authored-By: Claude
Apply review suggestion to both product variants of the example. Co-Authored-By: Claude
ritwika314
force-pushed
the
ritwika/db-naming-limits
branch
from
October 29, 2026 13:57
d4998f3 to
38b2977
Compare
ritwika314
marked this pull request as ready for review
October 29, 2026 14:07
sanderson
approved these changes
Oct 29, 2026
jstirnaman
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Core, Enterprise, and Cloud allow database names up to 511 ASCII characters, with at most one slash as a v1 retention policy separator.
Dedicated and Clustered keep the 64-character limit; the shared naming page now shows each product its own rules and examples.
Co-Authored-By: Claude