fix(influxdb-v1): correct FUTURE LIMIT and PAST LIMIT clause order and add to ALTER RETENTION POLICY #6591
+249
−217
Conversation
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
…d add to ALTER RETENTION POLICY - Fix clause order: FUTURE LIMIT must appear before PAST LIMIT (parser requirement) - Add FUTURE LIMIT and PAST LIMIT clauses to ALTER RETENTION POLICY syntax - Add grammar definitions for retention_future_limit and retention_past_limit - Add explicit note clarifying the required clause order - Fix "There are" style issue in spec.md closes #6590
influxdb/v1: - Simplify introduction and use relative anchor links - Convert notes to GitHub-style callout syntax - Fix heading hierarchy (Letters/digits, Identifiers, Keywords, Literals as h3) - Standardize Duration units table heading - Fix "keywords" typo - Reword "See FAQ" to "For more information, see" - Simplify KILL QUERY section - Fix SHOW MEASUREMENT CARDINALITY heading level - Replace "There are" with active voice enterprise_influxdb/v1: - Add related links to frontmatter - Simplify introduction and use relative anchor links - Convert notes to GitHub-style callout syntax - Add Characters and Letters/digits to TOC - Standardize Duration units table heading - Fix "keywords" typo - Reword "See FAQ" to "For more information, see" - Simplify KILL QUERY section for Enterprise clusters - Update SHOW TAG KEYS grammar to include with_key_clause - Remove backticks from SHOW STATS headings
jstirnaman
commented
Dec 4, 2025
| show_stats_stmt = "SHOW STATS [ FOR '<component>' | 'indexes' ]" | ||
| ``` | ||
|
|
||
| #### `SHOW STATS` |
Contributor
Author
There was a problem hiding this comment.
Duplicate heading. I rearranged the content to be consistent with Ent.
jstirnaman
commented
Dec 4, 2025
| - A multi-line comment begins with `/*` and ends with `*/`. This comment type can span several lines. | ||
| Multi-line comments do not support nested multi-line comments. | ||
|
|
||
| ## Query Engine Internals |
Contributor
Author
There was a problem hiding this comment.
If you're looking for this in Ent., it has a separate Internals page.
sanderson
approved these changes
Dec 5, 2025
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.
Summary
FUTURE LIMITmust appear beforePAST LIMIT(parser requirement)FUTURE LIMITandPAST LIMITclauses toALTER RETENTION POLICYsyntax documentationretention_future_limitandretention_past_limitFiles changed
Retention policy fixes
content/influxdb/v1/query_language/manage-database.mdcontent/enterprise_influxdb/v1/query_language/manage-database.mdcontent/influxdb/v1/query_language/spec.mdcontent/enterprise_influxdb/v1/query_language/spec.mdTest plan
closes #6590