fix(v1): remove incorrect FUTURE/PAST LIMIT ordering caution from OSS spec

The caution stated that prior to v1.12.3, PAST LIMIT must appear before
FUTURE LIMIT. This is incorrect — the correct syntax has always been
FUTURE LIMIT before PAST LIMIT. The v1.12.3 fix addresses Enterprise
meta-node recording of limits, not parser syntax order.
pull/6945/head
Jason Stirnaman 2026-03-14 15:00:49 -05:00
parent 3f6b969e81
commit 63fcdb7e4d
1 changed files with 0 additions and 12 deletions

View File

@ -389,12 +389,6 @@ create_database_stmt = "CREATE DATABASE" db_name
> [!Note]
> When using both `FUTURE LIMIT` and `PAST LIMIT` clauses, `FUTURE LIMIT` must appear before `PAST LIMIT`.
> [!Caution]
> **Prior to InfluxDB v1.12.3**, when using both `FUTURE LIMIT` and `PAST LIMIT` clauses,
> `PAST LIMIT` must appear before `FUTURE LIMIT`.
> [Upgrade to InfluxDB v1.12.3 or later](/influxdb/v1/about_the_project/release-notes/#v1123)
> to use the order shown above.
> [!Warning]
> Replication factors do not serve a purpose with single node instances.
@ -432,12 +426,6 @@ create_retention_policy_stmt = "CREATE RETENTION POLICY" policy_name on_clause
> [!Note]
> When using both `FUTURE LIMIT` and `PAST LIMIT` clauses, `FUTURE LIMIT` must appear before `PAST LIMIT`.
> [!Caution]
> **Prior to InfluxDB v1.12.3**, when using both `FUTURE LIMIT` and `PAST LIMIT` clauses,
> `PAST LIMIT` must appear before `FUTURE LIMIT`.
> [Upgrade to InfluxDB v1.12.3 or later](/influxdb/v1/about_the_project/release-notes/#v1123)
> to use the order shown above.
> [!Warning]
> Replication factors do not serve a purpose with single node instances.