Skip to content

Add v1.12.2 limitation callout for PAST LIMIT and FUTURE LIMIT #6607

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Copilot wants to merge 2 commits into
base: master
Choose a base branch
from
+16 −0
Draft

Add v1.12.2 limitation callout for PAST LIMIT and FUTURE LIMIT #6607

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c95bba7
Initial plan
Copilot Dec 10, 2025
fc39f20
Add v1.12.2 FUTURE LIMIT and PAST LIMIT callouts
Copilot Dec 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions content/enterprise_influxdb/v1/query_language/manage-database.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -317,6 +317,10 @@ For example, if a write request tries to write data to a retention policy with a
`PAST LIMIT 6h` and there are points in the request with timestamps older than
6 hours, those points are rejected.

> [!Important]
> In InfluxDB v1.12.2, `PAST LIMIT` cannot be changed after it is set.
> This will be fixed in a future release.

##### `FUTURE LIMIT` {metadata="v1.12.0+"}

The `FUTURE LIMIT` clause defines a time boundary after and relative to _now_
Expand All @@ -328,6 +332,10 @@ For example, if a write request tries to write data to a retention policy with a
`FUTURE LIMIT 6h` and there are points in the request with future timestamps
greater than 6 hours from now, those points are rejected.

> [!Important]
> In InfluxDB v1.12.2, `FUTURE LIMIT` cannot be changed after it is set.
> This will be fixed in a future release.

##### `DEFAULT`

Sets the new retention policy as the default retention policy for the database.
Expand Down
8 changes: 8 additions & 0 deletions content/influxdb/v1/query_language/manage-database.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -318,6 +318,10 @@ For example, if a write request tries to write data to a retention policy with a
`PAST LIMIT 6h` and there are points in the request with timestamps older than
6 hours, those points are rejected.

> [!Important]
> In InfluxDB v1.12.2, `PAST LIMIT` cannot be changed after it is set.
> This will be fixed in a future release.

##### `FUTURE LIMIT` {metadata="v1.12.0+"}

The `FUTURE LIMIT` clause defines a time boundary after and relative to _now_
Expand All @@ -329,6 +333,10 @@ For example, if a write request tries to write data to a retention policy with a
`FUTURE LIMIT 6h` and there are points in the request with future timestamps
greater than 6 hours from now, those points are rejected.

> [!Important]
> In InfluxDB v1.12.2, `FUTURE LIMIT` cannot be changed after it is set.
> This will be fixed in a future release.

##### `DEFAULT`

Sets the new retention policy as the default retention policy for the database.
Expand Down