Add v1.12.2 limitation callout for PAST LIMIT and FUTURE LIMIT (#6607)
* Initial plan * Add v1.12.2 FUTURE LIMIT and PAST LIMIT callouts Co-authored-by: jstirnaman <212227+jstirnaman@users.noreply.github.com> * fix(v1): Remove patch from Enterprise v1 name * fix(ent1): Remove version from `PAST LIMIT` and `FUTURE LIMIT` callout --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jstirnaman <212227+jstirnaman@users.noreply.github.com> Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>pull/6628/head^2
parent
5402a0a356
commit
0ba60f7d69
|
|
@ -6,7 +6,7 @@ aliases:
|
|||
- /enterprise/v1.11/
|
||||
menu:
|
||||
enterprise_influxdb_v1:
|
||||
name: InfluxDB Enterprise v1.11
|
||||
name: InfluxDB Enterprise v1
|
||||
weight: 1
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -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]
|
||||
> `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_
|
||||
|
|
@ -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]
|
||||
> `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.
|
||||
|
|
|
|||
|
|
@ -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]
|
||||
> `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_
|
||||
|
|
@ -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]
|
||||
> `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.
|
||||
|
|
|
|||
Loading…
Reference in New Issue