fix: broken links and formatting, missing Management API ReDoc security section for auth types
parent
6f8707363d
commit
18b90035a4
|
@ -40,6 +40,7 @@ tags:
|
||||||
See how to [create a management token](/influxdb3/cloud-dedicated/admin/tokens/management/).
|
See how to [create a management token](/influxdb3/cloud-dedicated/admin/tokens/management/).
|
||||||
|
|
||||||
By default, management tokens in InfluxDB 3 are short-lived tokens issued by an OAuth2 identity provider that grant a specific user administrative access to your InfluxDB cluster. However, for automation purposes, you can manually create management tokens that authenticate directly with your InfluxDB cluster and do not require human interaction with your identity provider.
|
By default, management tokens in InfluxDB 3 are short-lived tokens issued by an OAuth2 identity provider that grant a specific user administrative access to your InfluxDB cluster. However, for automation purposes, you can manually create management tokens that authenticate directly with your InfluxDB cluster and do not require human interaction with your identity provider.
|
||||||
|
<!-- ReDoc-Inject: <security-definitions> -->
|
||||||
- name: Database tokens
|
- name: Database tokens
|
||||||
description: Manage database read/write tokens for a cluster
|
description: Manage database read/write tokens for a cluster
|
||||||
- name: Databases
|
- name: Databases
|
||||||
|
|
|
@ -52,7 +52,7 @@ tags:
|
||||||
#### Related guides
|
#### Related guides
|
||||||
|
|
||||||
- [Manage tokens](/influxdb3/core/admin/tokens/)
|
- [Manage tokens](/influxdb3/core/admin/tokens/)
|
||||||
- [Authentication and authorization](/influxdb3/core/reference/authentication/)
|
- [Authentication and authorization](/influxdb3/core/reference/internals/authentication/)
|
||||||
x-traitTag: true
|
x-traitTag: true
|
||||||
- name: Cache data
|
- name: Cache data
|
||||||
description: |
|
description: |
|
||||||
|
|
|
@ -52,7 +52,7 @@ tags:
|
||||||
#### Related guides
|
#### Related guides
|
||||||
|
|
||||||
- [Manage tokens](/influxdb3/enterprise/admin/tokens/)
|
- [Manage tokens](/influxdb3/enterprise/admin/tokens/)
|
||||||
- [Authentication and authorization](/influxdb3/enterprise/reference/authentication/)
|
- [Authentication and authorization](/influxdb3/enterprise/reference/internals/authentication/)
|
||||||
x-traitTag: true
|
x-traitTag: true
|
||||||
- name: Cache data
|
- name: Cache data
|
||||||
description: |
|
description: |
|
||||||
|
@ -1936,8 +1936,6 @@ components:
|
||||||
scheme: bearer
|
scheme: bearer
|
||||||
bearerFormat: JWT
|
bearerFormat: JWT
|
||||||
description: |
|
description: |
|
||||||
_During Alpha release, an API token is not required._
|
|
||||||
|
|
||||||
A Bearer token for authentication.
|
A Bearer token for authentication.
|
||||||
|
|
||||||
Provide the scheme and the API token in the `Authorization` header--for example:
|
Provide the scheme and the API token in the `Authorization` header--for example:
|
||||||
|
|
|
@ -13,7 +13,7 @@ related:
|
||||||
- /influxdb3/core/reference/cli/influxdb3/query/
|
- /influxdb3/core/reference/cli/influxdb3/query/
|
||||||
- /influxdb3/core/reference/sql/
|
- /influxdb3/core/reference/sql/
|
||||||
- /influxdb3/core/reference/influxql/
|
- /influxdb3/core/reference/influxql/
|
||||||
# - /influxdb3/core/get-started/query/#execute-an-sql-query, Get started querying data
|
# - /influxdb3/core/query-data/execute-queries/, Get started querying data
|
||||||
list_code_example: |
|
list_code_example: |
|
||||||
```sh
|
```sh
|
||||||
influxdb3 query \
|
influxdb3 query \
|
||||||
|
|
|
@ -13,7 +13,7 @@ related:
|
||||||
- /influxdb3/enterprise/reference/cli/influxdb3/query/
|
- /influxdb3/enterprise/reference/cli/influxdb3/query/
|
||||||
- /influxdb3/enterprise/reference/sql/
|
- /influxdb3/enterprise/reference/sql/
|
||||||
- /influxdb3/enterprise/reference/influxql/
|
- /influxdb3/enterprise/reference/influxql/
|
||||||
# - /influxdb3/enterprise/get-started/query/#execute-an-sql-query, Get started querying data
|
# - /influxdb3/enterprise/query-data/execute-queries/, Get started querying data
|
||||||
list_code_example: |
|
list_code_example: |
|
||||||
```sh
|
```sh
|
||||||
influxdb3 query \
|
influxdb3 query \
|
||||||
|
|
|
@ -8,5 +8,5 @@ For more information, see the [C# client example on GitHub](https://github.com/a
|
||||||
> We recommend using the [`influxdb3-csharp` C# client library](/influxdb3/version/reference/client-libraries/v3/csharp/) for integrating InfluxDB 3 with your C# application code.
|
> We recommend using the [`influxdb3-csharp` C# client library](/influxdb3/version/reference/client-libraries/v3/csharp/) for integrating InfluxDB 3 with your C# application code.
|
||||||
>
|
>
|
||||||
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||||
> and provide convenient methods for [writing](/influxdb3/version/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/version/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
> and provide convenient methods for [writing](/influxdb3/version/write-data/api-client-libraries/), [querying](/influxdb3/version/query-data/execute-queries/), and processing data stored in {{% product-name %}}.
|
||||||
> Client libraries can query using SQL or InfluxQL.
|
> Client libraries can query using SQL or InfluxQL.
|
||||||
|
|
|
@ -6,7 +6,7 @@
|
||||||
> We recommend using the [`influxdb3-go` Go client library](/influxdb3/version/reference/client-libraries/v3/go/) for integrating InfluxDB 3 with your Go application code.
|
> We recommend using the [`influxdb3-go` Go client library](/influxdb3/version/reference/client-libraries/v3/go/) for integrating InfluxDB 3 with your Go application code.
|
||||||
>
|
>
|
||||||
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||||
> and provide convenient methods for [writing](/influxdb3/version/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/version/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
> and provide convenient methods for [writing](/influxdb3/version/write-data/api-client-libraries/), [querying](/influxdb3/version/query-data/execute-queries/), and processing data stored in {{% product-name %}}.
|
||||||
> Client libraries can query using SQL or InfluxQL.
|
> Client libraries can query using SQL or InfluxQL.
|
||||||
|
|
||||||
## Flight SQL client
|
## Flight SQL client
|
||||||
|
|
|
@ -6,7 +6,7 @@
|
||||||
> We recommend using the [`influxdb3-java` Java client library](/influxdb3/version/reference/client-libraries/v3/java/) for integrating InfluxDB 3 with your Java application code.
|
> We recommend using the [`influxdb3-java` Java client library](/influxdb3/version/reference/client-libraries/v3/java/) for integrating InfluxDB 3 with your Java application code.
|
||||||
>
|
>
|
||||||
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||||
> and provide convenient methods for [writing](/influxdb3/version/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/version/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
> and provide convenient methods for [writing](/influxdb3/version/write-data/api-client-libraries/), [querying](/influxdb3/version/query-data/execute-queries/), and processing data stored in {{% product-name %}}.
|
||||||
> Client libraries can query using SQL or InfluxQL.
|
> Client libraries can query using SQL or InfluxQL.
|
||||||
|
|
||||||
<!-- TOC -->
|
<!-- TOC -->
|
||||||
|
|
|
@ -6,21 +6,20 @@
|
||||||
> We recommend using the [`influxdb3-python` Python client library](/influxdb3/version/reference/client-libraries/v3/python/) for integrating InfluxDB 3 with your Python application code.
|
> We recommend using the [`influxdb3-python` Python client library](/influxdb3/version/reference/client-libraries/v3/python/) for integrating InfluxDB 3 with your Python application code.
|
||||||
>
|
>
|
||||||
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||||
> and provide convenient methods for [writing](/influxdb3/version/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/version/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
> and provide convenient methods for [writing](/influxdb3/version/write-data/api-client-libraries/), [querying](/influxdb3/version/query-data/execute-queries/), and processing data stored in {{% product-name %}}.
|
||||||
> Client libraries can query using SQL or InfluxQL.
|
> Client libraries can query using SQL or InfluxQL.
|
||||||
|
|
||||||
The following examples show how to use the `pyarrow.flight` and `pandas` Python modules to query and format data stored in an {{% product-name %}} database:
|
The following examples show how to use the `pyarrow.flight` and `pandas` Python modules to query and format data stored in an {{% product-name %}} database:
|
||||||
|
|
||||||
{{% code-tabs-wrapper %}}
|
{{< code-tabs-wrapper >}}
|
||||||
{{% code-tabs %}}
|
{{% code-tabs %}}
|
||||||
[SQL](#sql-python)
|
[SQL](#sql-python)
|
||||||
[InfluxQL](#influxql-python)
|
[InfluxQL](#influxql-python)
|
||||||
{{% /code-tabs %}}
|
{{% /code-tabs %}}
|
||||||
|
|
||||||
{{% code-tab-content %}}
|
{{% code-tab-content %}}
|
||||||
<!-- BEGIN SQL -->
|
<!-- BEGIN SQL -->
|
||||||
{{% code-placeholders "DATABASE_NAME|DATABASE_TOKEN" %}}
|
{{% code-placeholders "DATABASE_NAME|DATABASE_TOKEN" %}}
|
||||||
```py
|
```python
|
||||||
# Using pyarrow>=12.0.0 FlightClient
|
# Using pyarrow>=12.0.0 FlightClient
|
||||||
from pyarrow.flight import FlightClient, Ticket, FlightCallOptions
|
from pyarrow.flight import FlightClient, Ticket, FlightCallOptions
|
||||||
import json
|
import json
|
||||||
|
@ -62,7 +61,7 @@ print(data_frame.to_markdown())
|
||||||
{{% code-tab-content %}}
|
{{% code-tab-content %}}
|
||||||
<!-- BEGIN INFLUXQL -->
|
<!-- BEGIN INFLUXQL -->
|
||||||
{{% code-placeholders "DATABASE_NAME|DATABASE_TOKEN" %}}
|
{{% code-placeholders "DATABASE_NAME|DATABASE_TOKEN" %}}
|
||||||
```py
|
```python
|
||||||
# Using pyarrow>=12.0.0 FlightClient
|
# Using pyarrow>=12.0.0 FlightClient
|
||||||
from pyarrow.flight import FlightClient, Ticket, FlightCallOptions
|
from pyarrow.flight import FlightClient, Ticket, FlightCallOptions
|
||||||
import json
|
import json
|
||||||
|
@ -97,6 +96,7 @@ print(data_frame.to_markdown())
|
||||||
{{% /code-placeholders %}}
|
{{% /code-placeholders %}}
|
||||||
<!-- END INFLUXQL -->
|
<!-- END INFLUXQL -->
|
||||||
{{% /code-tab-content %}}
|
{{% /code-tab-content %}}
|
||||||
|
{{< /code-tabs-wrapper >}}
|
||||||
|
|
||||||
Replace the following:
|
Replace the following:
|
||||||
|
|
||||||
|
@ -104,5 +104,3 @@ Replace the following:
|
||||||
- {{% code-placeholder-key %}}`DATABASE_TOKEN`{{% /code-placeholder-key %}}:
|
- {{% code-placeholder-key %}}`DATABASE_TOKEN`{{% /code-placeholder-key %}}:
|
||||||
a [database token](/influxdb3/version/admin/tokens/database/)
|
a [database token](/influxdb3/version/admin/tokens/database/)
|
||||||
with sufficient permissions to the specified database
|
with sufficient permissions to the specified database
|
||||||
|
|
||||||
{{% /code-tabs-wrapper %}}
|
|
||||||
|
|
|
@ -6,7 +6,7 @@ The [Python `flightsql-dbapi` Flight SQL DBAPI library](https://github.com/influ
|
||||||
> We recommend using the [`influxdb3-python` Python client library](/influxdb3/version/reference/client-libraries/v3/python/) for integrating InfluxDB 3 with your Python application code.
|
> We recommend using the [`influxdb3-python` Python client library](/influxdb3/version/reference/client-libraries/v3/python/) for integrating InfluxDB 3 with your Python application code.
|
||||||
>
|
>
|
||||||
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
> [InfluxDB 3 client libraries](/influxdb3/version/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||||
> and provide convenient methods for [writing](/influxdb3/version/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/version/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
> and provide convenient methods for [writing](/influxdb3/version/write-data/api-client-libraries/), [querying](/influxdb3/version/query-data/execute-queries/), and processing data stored in {{% product-name %}}.
|
||||||
> Client libraries can query using SQL or InfluxQL.
|
> Client libraries can query using SQL or InfluxQL.
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
|
@ -32,7 +32,7 @@ from flightsql import FlightSQLClient
|
||||||
```
|
```
|
||||||
|
|
||||||
- `flightsql.FlightSQLClient` class: an interface for [initializing
|
- `flightsql.FlightSQLClient` class: an interface for [initializing
|
||||||
a client](#initialization) and interacting with a Flight SQL server.
|
a client](#initialize-a-client) and interacting with a Flight SQL server.
|
||||||
|
|
||||||
## API reference
|
## API reference
|
||||||
|
|
||||||
|
@ -41,11 +41,11 @@ a client](#initialization) and interacting with a Flight SQL server.
|
||||||
- [Initialize a client](#initialize-a-client)
|
- [Initialize a client](#initialize-a-client)
|
||||||
- [Instance methods](#instance-methods)
|
- [Instance methods](#instance-methods)
|
||||||
- [FlightSQLClient.execute](#flightsqlclientexecute)
|
- [FlightSQLClient.execute](#flightsqlclientexecute)
|
||||||
- [Syntax {#execute-query-syntax}](#syntax-execute-query-syntax)
|
- [Syntax](#execute-query-syntax)
|
||||||
- [Example {#execute-query-example}](#example-execute-query-example)
|
- [Example](#execute-query-example)
|
||||||
- [FlightSQLClient.do_get](#flightsqlclientdo_get)
|
- [FlightSQLClient.do_get](#flightsqlclientdo_get)
|
||||||
- [Syntax {#retrieve-data-syntax}](#syntax-retrieve-data-syntax)
|
- [Syntax](#retrieve-data-syntax)
|
||||||
- [Example {#retrieve-data-example}](#example-retrieve-data-example)
|
- [Example](#retrieve-data-example)
|
||||||
|
|
||||||
## Class FlightSQLClient
|
## Class FlightSQLClient
|
||||||
|
|
||||||
|
|
|
@ -41,7 +41,7 @@ Write requests return the following status codes:
|
||||||
| :-------------------------------| :--------------------------------------------------------------- | :------------- |
|
| :-------------------------------| :--------------------------------------------------------------- | :------------- |
|
||||||
| `204 "Success"` | | If InfluxDB ingested the data |
|
| `204 "Success"` | | If InfluxDB ingested the data |
|
||||||
| `400 "Bad request"` | error details about rejected points, up to 100 points: `line` contains the first rejected line, `message` describes rejections | If some or all request data isn't allowed (for example, if it is malformed or falls outside of the bucket's retention period)--the response body indicates whether a partial write has occurred or if all data has been rejected |
|
| `400 "Bad request"` | error details about rejected points, up to 100 points: `line` contains the first rejected line, `message` describes rejections | If some or all request data isn't allowed (for example, if it is malformed or falls outside of the bucket's retention period)--the response body indicates whether a partial write has occurred or if all data has been rejected |
|
||||||
| `401 "Unauthorized"` | | If the `Authorization` header is missing or malformed or if the [token](/influxdb3/version/admin/tokens/) doesn't have [permission](/influxdb3/version/reference/cli/influxctl/token/create/#examples) to write to the database. See [examples using credentials](/influxdb3/version/get-started/write/#write-line-protocol-to-influxdb) in write requests. |
|
| `401 "Unauthorized"` | | If the `Authorization` header is missing or malformed or if the [token](/influxdb3/version/admin/tokens/) doesn't have [permission](/influxdb3/version/reference/cli/influxctl/token/create/#examples) to write to the database. See [examples using credentials](/influxdb3/version/write-data/api-client-libraries/) in write requests. |
|
||||||
| `404 "Not found"` | requested **resource type** (for example, "organization" or "database"), and **resource name** | If a requested resource (for example, organization or database) wasn't found |
|
| `404 "Not found"` | requested **resource type** (for example, "organization" or "database"), and **resource name** | If a requested resource (for example, organization or database) wasn't found |
|
||||||
| `500 "Internal server error"` | | Default status for an error |
|
| `500 "Internal server error"` | | Default status for an error |
|
||||||
| `503` "Service unavailable" | | If the server is temporarily unavailable to accept writes. The `Retry-After` header describes when to try the write again.
|
| `503` "Service unavailable" | | If the server is temporarily unavailable to accept writes. The `Retry-After` header describes when to try the write again.
|
||||||
|
|
Loading…
Reference in New Issue