From 6c76ace5974f4798789ab7fa9b082dc210845dfe Mon Sep 17 00:00:00 2001 From: Jason Stirnaman Date: Thu, 15 Feb 2024 17:15:39 -0600 Subject: [PATCH] fix(v2): (Closes #5320) Remove attribute from OSS /api/v2/query schema. OSS doesn't support parameterized queries. See upstream PR: https://github.com/influxdata/openapi/pull/646 --- api-docs/v2/ref.yml | 29 +---------------------------- 1 file changed, 1 insertion(+), 28 deletions(-) diff --git a/api-docs/v2/ref.yml b/api-docs/v2/ref.yml index 703b76f7f3..01673a1aae 100644 --- a/api-docs/v2/ref.yml +++ b/api-docs/v2/ref.yml @@ -3453,7 +3453,7 @@ components: description: | The schema Type. Default is `implicit`. - #### InfluxDB Cloud + #### InfluxDB Cloud v2 - Use `explicit` to enforce column names, tags, fields, and data types for your data. @@ -3513,33 +3513,6 @@ components: Default is the server `now` time. format: date-time type: string - params: - additionalProperties: true - description: | - Key-value pairs passed as parameters during query execution. - - To use parameters in your query, pass a _`query`_ with `params` references (in dot notation)--for example: - - ```json - query: "from(bucket: params.mybucket)\ - |> range(start: params.rangeStart) |> limit(n:1)" - ``` - - and pass _`params`_ with the key-value pairs--for example: - - ```json - params: { - "mybucket": "environment", - "rangeStart": "-30d" - } - ``` - - During query execution, InfluxDB passes _`params`_ to your script and substitutes the values. - - #### Limitations - - - If you use _`params`_, you can't use _`extern`_. - type: object query: description: The query script to execute. type: string