Skip to content
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

fix(v2): (Closes #5320) Remove attribute from OSS /api/v2/query sch… #5325

Merged
merged 1 commit into from
Feb 15, 2024
Merged

fix(v2): (Closes #5320) Remove attribute from OSS /api/v2/query sch… #5325

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
29 changes: 1 addition & 28 deletions api-docs/v2/ref.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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
Expand Down