Merge branch 'monolith' into pd/update-getting-started
commit
26321a33be
|
@ -38,7 +38,7 @@ to visualize data from your **InfluxDB Enterprise** cluster.
|
|||
supported by InfluxDB {{< current-version >}} (InfluxQL or Flux):
|
||||
|
||||
{{% note %}}
|
||||
SQL is only supported in InfluxDB v3.
|
||||
SQL is only supported in InfluxDB 3.
|
||||
{{% /note %}}
|
||||
|
||||
{{< tabs-wrapper >}}
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: The future of Flux
|
||||
description: >
|
||||
Flux is in maintenance mode and is not supported in InfluxDB v3.
|
||||
Flux is in maintenance mode and is not supported in InfluxDB 3.
|
||||
This decision was based on the broad demand for native SQL and the continued
|
||||
growth and adoption of InfluxQL.
|
||||
menu:
|
||||
|
@ -10,18 +10,18 @@ menu:
|
|||
weight: 15
|
||||
---
|
||||
|
||||
Flux is in maintenance mode and is not supported in InfluxDB v3 due to the broad
|
||||
Flux is in maintenance mode and is not supported in InfluxDB 3 due to the broad
|
||||
demand for native SQL and the continued growth and adoption of InfluxQL.
|
||||
|
||||
InfluxData continues to support Flux for InfluxDB 1.x and 2.x, and you can
|
||||
continue using it without changing your code.
|
||||
If interested in transitioning to InfluxDB v3 and you want to future-proof your
|
||||
If interested in transitioning to InfluxDB 3 and you want to future-proof your
|
||||
code, we suggest using InfluxQL.
|
||||
|
||||
As we developed InfluxDB v3, our top priority was improving performance at the
|
||||
As we developed InfluxDB 3, our top priority was improving performance at the
|
||||
database layer: faster ingestion, better compression, enhanced querying,
|
||||
and more scalability. However, this meant we couldn’t bring everything forward
|
||||
from v2. As InfluxDB v3 is a ground-up rewrite of the database in a new language
|
||||
from v2. As InfluxDB 3 is a ground-up rewrite of the database in a new language
|
||||
(from Go to Rust), we couldn’t bring Flux forward to v3.
|
||||
|
||||
- [What do you mean by Flux is in maintenance mode?](#what-do-you-mean-by-flux-is-in-maintenance-mode)
|
||||
|
@ -33,7 +33,7 @@ from v2. As InfluxDB v3 is a ground-up rewrite of the database in a new language
|
|||
We still support Flux, but are not actively developing any new Flux features.
|
||||
We will continue to provide security patches and will address any critical
|
||||
defects through the maintenance period.
|
||||
Our focus is our latest database engine, InfluxDB v3, and its associated products.
|
||||
Our focus is our latest database engine, InfluxDB 3, and its associated products.
|
||||
|
||||
## Is Flux going to End-of-Life?
|
||||
|
||||
|
@ -44,7 +44,7 @@ future-proof your code, we recommend using InfluxQL or SQL.
|
|||
|
||||
## What alternatives do you have for Flux tasks?
|
||||
|
||||
If moving to InfluxDB v3, you can't bring Flux tasks because InfluxDB v3 doesn't
|
||||
If moving to InfluxDB 3, you can't bring Flux tasks because InfluxDB 3 doesn't
|
||||
support Flux natively. When you move to v3, you will need to rewrite your tasks
|
||||
using whatever technologies your team prefers. However, if you’re using tasks
|
||||
for downsampling specifically, the storage performance in v3 is much better so
|
||||
|
|
|
@ -25,13 +25,13 @@ To switch {{< product-name "short" >}} organizations:
|
|||
{{% note %}}
|
||||
#### Migrate to InfluxDB Cloud Serverless
|
||||
|
||||
To unlock the benefits of the InfluxDB v3 storage engine, including unlimited
|
||||
To unlock the benefits of the InfluxDB 3 storage engine, including unlimited
|
||||
cardinality and SQL, [migrate your data to an InfluxDB Cloud Serverless organization](/influxdb3/cloud-serverless/write-data/migrate-data/migrate-tsm-to-serverless/).
|
||||
|
||||
All InfluxDB Cloud [accounts](/influxdb3/cloud-serverless/admin/accounts/) and
|
||||
[organizations](/influxdb3/cloud-serverless/admin/organizations/) created through
|
||||
[cloud2.influxdata.com](https://cloud2.influxdata.com) on or after **January 31, 2023**
|
||||
are on InfluxDB Cloud Serverless and are powered by the InfluxDB v3 storage engine.
|
||||
are on InfluxDB Cloud Serverless and are powered by the InfluxDB 3 storage engine.
|
||||
|
||||
To see which storage engine your organization uses, find the **InfluxDB Cloud powered by**
|
||||
link in your [InfluxDB Cloud organization homepage](https://cloud2.influxdata.com)
|
||||
|
|
|
@ -28,13 +28,13 @@ The following articles provide information about managing organizations:
|
|||
{{% note %}}
|
||||
#### Migrate to InfluxDB Cloud Serverless
|
||||
|
||||
To unlock the benefits of the InfluxDB v3 storage engine, including unlimited
|
||||
To unlock the benefits of the InfluxDB 3 storage engine, including unlimited
|
||||
cardinality and SQL, [migrate your data to an InfluxDB Cloud Serverless organization](/influxdb3/cloud-serverless/write-data/migrate-data/migrate-tsm-to-serverless/).
|
||||
|
||||
All InfluxDB Cloud [accounts](/influxdb3/cloud-serverless/admin/accounts/) and
|
||||
[organizations](/influxdb3/cloud-serverless/admin/organizations/) created through
|
||||
[cloud2.influxdata.com](https://cloud2.influxdata.com) on or after **January 31, 2023**
|
||||
are on InfluxDB Cloud Serverless and are powered by the InfluxDB v3 storage engine.
|
||||
are on InfluxDB Cloud Serverless and are powered by the InfluxDB 3 storage engine.
|
||||
|
||||
To see which storage engine your organization uses, find the **InfluxDB Cloud powered by**
|
||||
link in your [InfluxDB Cloud organization homepage](https://cloud2.influxdata.com)
|
||||
|
|
|
@ -22,9 +22,9 @@ walks through the migration.
|
|||
The specific process varies depending on whether your destination account is
|
||||
powered by our current database engine,
|
||||
[Time-Structured Merge Tree (TSM)](/influxdb/v2/reference/internals/storage-engine/#time-structured-merge-tree-tsm)
|
||||
or [our new database engine, InfluxDB v3](/blog/announcing-general-availability-new-database-engine/).
|
||||
or [our new database engine, InfluxDB 3](/blog/announcing-general-availability-new-database-engine/).
|
||||
|
||||
To benefit from the InfluxDB v3 storage engine's unlimited cardinality and
|
||||
To benefit from the InfluxDB 3 storage engine's unlimited cardinality and
|
||||
support for SQL, migrate your data to InfluxDB Cloud Serverless.
|
||||
|
||||
- [Migrate data TSM to Serverless](/influxdb3/cloud-serverless/write-data/migrate-data/migrate-tsm-to-serverless/)
|
||||
|
|
|
@ -13,13 +13,13 @@ weight: 11
|
|||
{{% note %}}
|
||||
#### Migrate to InfluxDB Cloud Serverless
|
||||
|
||||
To unlock the benefits of the InfluxDB v3 storage engine, including unlimited
|
||||
To unlock the benefits of the InfluxDB 3 storage engine, including unlimited
|
||||
cardinality and SQL, [migrate your data to an InfluxDB Cloud Serverless organization](/influxdb3/cloud-serverless/write-data/migrate-data/migrate-tsm-to-serverless/).
|
||||
|
||||
All InfluxDB Cloud [accounts](/influxdb3/cloud-serverless/admin/accounts/) and
|
||||
[organizations](/influxdb3/cloud-serverless/admin/organizations/) created through
|
||||
[cloud2.influxdata.com](https://cloud2.influxdata.com) on or after **January 31, 2023**
|
||||
are on InfluxDB Cloud Serverless and are powered by the InfluxDB v3 storage engine.
|
||||
are on InfluxDB Cloud Serverless and are powered by the InfluxDB 3 storage engine.
|
||||
|
||||
To see which storage engine your organization uses, find the **InfluxDB Cloud powered by**
|
||||
link in your [InfluxDB Cloud organization homepage](https://cloud2.influxdata.com)
|
||||
|
|
|
@ -405,13 +405,13 @@ internal error: error calling function "metadata" @97:1-97:11: error calling fun
|
|||
|
||||
### Migrate to InfluxDB Cloud Serverless
|
||||
|
||||
To unlock the benefits of the InfluxDB v3 storage engine, including unlimited
|
||||
To unlock the benefits of the InfluxDB 3 storage engine, including unlimited
|
||||
cardinality and SQL, [migrate your data to an InfluxDB Cloud Serverless organization](/influxdb3/cloud-serverless/write-data/migrate-data/migrate-tsm-to-serverless/).
|
||||
|
||||
All InfluxDB Cloud [accounts](/influxdb3/cloud-serverless/admin/accounts/) and
|
||||
[organizations](/influxdb3/cloud-serverless/admin/organizations/) created through
|
||||
[cloud2.influxdata.com](https://cloud2.influxdata.com) on or after **January 31, 2023**
|
||||
are on InfluxDB Cloud Serverless and are powered by the InfluxDB v3 storage engine.
|
||||
are on InfluxDB Cloud Serverless and are powered by the InfluxDB 3 storage engine.
|
||||
|
||||
To see which storage engine your organization uses, find the **InfluxDB Cloud powered by**
|
||||
link in your [InfluxDB Cloud organization homepage](https://cloud2.influxdata.com)
|
||||
|
|
|
@ -25,8 +25,8 @@ alt_links:
|
|||
This release represents the first public release of InfluxDB OSS v1 since 2021
|
||||
and includes many enhancements and bug fixes added to InfluxDB Enterprise and
|
||||
then back-ported to InfluxDB OSS v1. Many of these enhancements improve
|
||||
compatibility between InfluxDB v1 and InfluxDB v3 and help to ease the migration
|
||||
of InfluxDB v1 workloads to InfluxDB v3.
|
||||
compatibility between InfluxDB v1 and InfluxDB 3 and help to ease the migration
|
||||
of InfluxDB v1 workloads to InfluxDB 3.
|
||||
|
||||
{{% warn %}}
|
||||
#### Before upgrading to InfluxDB 1.11
|
||||
|
|
|
@ -26,33 +26,33 @@ or the client of your choice.
|
|||
{{% note %}}
|
||||
If you're getting started with InfluxDB v1, we recommend using the
|
||||
InfluxDB v1 client libraries and InfluxQL for
|
||||
[InfluxDB v3 compatibility](/influxdb/v1/tools/api/#influxdb-v3-compatibility).
|
||||
[InfluxDB 3 compatibility](/influxdb/v1/tools/api/#influxdb-3-compatibility).
|
||||
{{% /note %}}
|
||||
|
||||
The following sections assume your InfluxDB instance is running on `localhost`
|
||||
port `8086` and HTTPS is not enabled.
|
||||
Those settings [are configurable](/influxdb/v1/administration/config/#http-endpoints-settings).
|
||||
|
||||
- [InfluxDB v3 compatibility](#influxdb-v3-compatibility)
|
||||
- [InfluxDB 3 compatibility](#influxdb-3-compatibility)
|
||||
- [InfluxDB 2.x API compatibility endpoints](#influxdb-2x-api-compatibility-endpoints)
|
||||
- [InfluxDB 1.x HTTP endpoints](#influxdb-1x-http-endpoints)
|
||||
|
||||
## InfluxDB v3 compatibility
|
||||
## InfluxDB 3 compatibility
|
||||
|
||||
InfluxDB v3 is InfluxDB’s next generation that allows
|
||||
InfluxDB 3 is InfluxDB’s next generation that allows
|
||||
infinite series cardinality without impact on overall database performance, and
|
||||
brings native SQL support and improved InfluxQL performance.
|
||||
|
||||
InfluxDB v3 supports the v1 `/write` and `/query` HTTP API endpoints.
|
||||
InfluxDB v3 isn't optimized for Flux.
|
||||
InfluxDB 3 supports the v1 `/write` and `/query` HTTP API endpoints.
|
||||
InfluxDB 3 isn't optimized for Flux.
|
||||
|
||||
If you're getting started with InfluxDB v1, we recommend using the
|
||||
InfluxDB v1 client libraries and InfluxQL.
|
||||
When you're ready, you can migrate to InfluxDB v3 and continue using the v1 client
|
||||
When you're ready, you can migrate to InfluxDB 3 and continue using the v1 client
|
||||
libraries as you gradually move your query workloads to use the v3 client libraries
|
||||
(and the v3 Flight API).
|
||||
|
||||
For more information, see [API compatibility and migration guides for InfluxDB v3](/influxdb3/cloud-dedicated/guides).
|
||||
For more information, see [API compatibility and migration guides for InfluxDB 3](/influxdb3/cloud-dedicated/guides).
|
||||
|
||||
## InfluxDB 2.x API compatibility endpoints
|
||||
|
||||
|
|
|
@ -20,7 +20,7 @@ with the InfluxDB v2 API and support both **InfluxDB 1.8+** and **InfluxDB 2.x**
|
|||
{{% note %}}
|
||||
If you're getting started with InfluxDB v1, we recommend using the
|
||||
InfluxDB v1 client libraries and InfluxQL for
|
||||
[InfluxDB v3 compatibility](/influxdb/v1/tools/api/#influxdb-v3-compatibility).
|
||||
[InfluxDB 3 compatibility](/influxdb/v1/tools/api/#influxdb-3-compatibility).
|
||||
|
||||
For more information about API and client library compatibility, see the
|
||||
[InfluxDB v1 API reference](/influxdb/v1/tools/api/).
|
||||
|
|
|
@ -40,7 +40,7 @@ to visualize data from your **InfluxDB v1.11** instance.
|
|||
supported by InfluxDB {{< current-version >}} (InfluxQL or Flux):
|
||||
|
||||
{{% note %}}
|
||||
SQL is only supported in InfluxDB v3.
|
||||
SQL is only supported in InfluxDB 3.
|
||||
{{% /note %}}
|
||||
|
||||
{{< tabs-wrapper >}}
|
||||
|
|
|
@ -592,7 +592,7 @@ See [line protocol](/influxdb/v2/reference/syntax/line-protocol/).
|
|||
The part of InfluxDB's structure that describes the data stored in the associated fields.
|
||||
Measurements are strings.
|
||||
|
||||
{{% cloud-only %}}With **InfluxDB v3**, a time series measurement equates to a relational database table with fields, tags, and timestamp as columns.{{% /cloud-only %}}
|
||||
{{% cloud-only %}}With **InfluxDB 3**, a time series measurement equates to a relational database table with fields, tags, and timestamp as columns.{{% /cloud-only %}}
|
||||
|
||||
Related entries: [field](#field), [series](#series), [table](#table)
|
||||
|
||||
|
@ -762,7 +762,7 @@ Related entries: [measurement](#measurement), [tag set](#tag-set), [field set](#
|
|||
|
||||
### primary key
|
||||
|
||||
With the InfluxDB v3 storage engine, the primary key is the list of columns
|
||||
With the InfluxDB 3 storage engine, the primary key is the list of columns
|
||||
used to uniquely identify each row in a table.
|
||||
Rows are uniquely identified by their timestamp and tag set.
|
||||
|
||||
|
@ -1079,7 +1079,7 @@ Flux processes a series of tables for a specified time series.
|
|||
These tables in sequence result in a stream of data.
|
||||
{{% /oss-only %}}
|
||||
|
||||
{{% cloud-only %}}With **InfluxDB v3**, a time series measurement equates to a relational database table with fields, tags, and timestamp as columns.{{% /cloud-only %}}
|
||||
{{% cloud-only %}}With **InfluxDB 3**, a time series measurement equates to a relational database table with fields, tags, and timestamp as columns.{{% /cloud-only %}}
|
||||
|
||||
Related entries: [measurement](#measurement)
|
||||
|
||||
|
|
|
@ -38,7 +38,7 @@ The instructions in this guide require **Grafana Cloud** or **Grafana 10.3+**.
|
|||
supported by InfluxDB {{< current-version >}} (Flux or InfluxQL):
|
||||
|
||||
{{% note %}}
|
||||
SQL is only supported in InfluxDB v3.
|
||||
SQL is only supported in InfluxDB 3.
|
||||
{{% /note %}}
|
||||
|
||||
{{< tabs-wrapper >}}
|
||||
|
|
|
@ -21,13 +21,13 @@ time series use case.
|
|||
<a class="btn" href="{{< cta-link >}}">Request an InfluxDB Cloud Dedicated cluster</a>
|
||||
<a class="btn" href="/influxdb3/cloud-dedicated/get-started/">Get started with InfluxDB Cloud Dedicated</a>
|
||||
|
||||
## InfluxDB 3.0
|
||||
## InfluxDB 3
|
||||
|
||||
**InfluxDB 3.0** is InfluxDB's next generation that unlocks series
|
||||
**InfluxDB 3** is InfluxDB's next generation that unlocks series
|
||||
limitations present in the Time Structured Merge Tree (TSM) storage engine and
|
||||
allows infinite series cardinality without any impact on overall database performance.
|
||||
It also brings native **SQL support** and improved InfluxQL performance.
|
||||
|
||||
View the following video for more information about InfluxDB 3.0:
|
||||
View the following video for more information about InfluxDB 3:
|
||||
|
||||
{{< youtube "uwqLWpmlQHM" >}}
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: View partition information
|
||||
description: >
|
||||
Query partition information from InfluxDB v3 system tables to view partition
|
||||
Query partition information from InfluxDB 3 system tables to view partition
|
||||
templates and verify partitions are working as intended.
|
||||
menu:
|
||||
influxdb3_cloud_dedicated:
|
||||
|
|
|
@ -185,7 +185,7 @@ The retention period value cannot be negative or contain whitespace.
|
|||
|
||||
{{< product-name >}} lets you define a custom partitioning strategy for each database.
|
||||
A _partition_ is a logical grouping of data stored in [Apache Parquet](https://parquet.apache.org/)
|
||||
format in the InfluxDB v3 storage engine. By default, data is partitioned by day,
|
||||
format in the InfluxDB 3 storage engine. By default, data is partitioned by day,
|
||||
but, depending on your schema and workload, customizing the partitioning
|
||||
strategy can improve query performance.
|
||||
|
||||
|
@ -329,7 +329,7 @@ The retention period value cannot be negative or contain whitespace.
|
|||
|
||||
{{< product-name >}} lets you define a custom partitioning strategy for each database.
|
||||
A _partition_ is a logical grouping of data stored in [Apache Parquet](https://parquet.apache.org/)
|
||||
format in the InfluxDB v3 storage engine. By default, data is partitioned by day,
|
||||
format in the InfluxDB 3 storage engine. By default, data is partitioned by day,
|
||||
but, depending on your schema and workload, customizing the partitioning
|
||||
strategy can improve query performance.
|
||||
|
||||
|
|
|
@ -222,7 +222,7 @@ Request rate is reported in bytes per second.
|
|||
|
||||
#### HTTP request error rate (server's POV at Router)
|
||||
|
||||
HTTP request error rate reported by the InfluxDB v3 HTTP request handler.
|
||||
HTTP request error rate reported by the InfluxDB 3 HTTP request handler.
|
||||
Error rate is represented the percentage in total requests that return a non-2xx
|
||||
response code.
|
||||
|
||||
|
|
|
@ -36,7 +36,7 @@ You can query the cluster system tables for information about your cluster.
|
|||
{{% warn %}}
|
||||
#### May impact cluster performance
|
||||
|
||||
Querying InfluxDB v3 system tables may impact write and query
|
||||
Querying InfluxDB 3 system tables may impact write and query
|
||||
performance of your {{< product-name omit=" Clustered" >}} cluster.
|
||||
Use filters to [optimize queries to reduce impact to your cluster](#optimize-queries-to-reduce-impact-to-your-cluster).
|
||||
|
||||
|
@ -133,7 +133,7 @@ tables may have on your cluster.
|
|||
|
||||
### Optimize queries to reduce impact to your cluster
|
||||
|
||||
Querying InfluxDB v3 system tables may impact the performance of your
|
||||
Querying InfluxDB 3 system tables may impact the performance of your
|
||||
{{< product-name omit=" Clustered" >}} cluster.
|
||||
As you write data to a cluster, the number of partitions and Parquet files
|
||||
can increase to a point that impacts system table performance.
|
||||
|
@ -393,7 +393,7 @@ The `system.compactor` table contains the following columns:
|
|||
{{% warn %}}
|
||||
#### May impact cluster performance
|
||||
|
||||
Querying InfluxDB v3 system tables may impact write and query
|
||||
Querying InfluxDB 3 system tables may impact write and query
|
||||
performance of your {{< product-name omit=" Clustered" >}} cluster.
|
||||
|
||||
The examples in this section include `WHERE` filters to [optimize queries and reduce impact to your cluster](#optimize-queries-to-reduce-impact-to-your-cluster).
|
||||
|
|
|
@ -61,7 +61,7 @@ influxctl table create \
|
|||
|
||||
{{< product-name >}} lets you define a custom partitioning strategy for each table.
|
||||
A _partition_ is a logical grouping of data stored in [Apache Parquet](https://parquet.apache.org/)
|
||||
format in the InfluxDB v3 storage engine. By default, data is partitioned by day,
|
||||
format in the InfluxDB 3 storage engine. By default, data is partitioned by day,
|
||||
but, depending on your schema and workload, customizing the partitioning
|
||||
strategy can improve query performance.
|
||||
|
||||
|
|
|
@ -12,7 +12,7 @@ influxdb3/cloud-dedicated/tags: [get-started]
|
|||
|
||||
InfluxDB is the platform purpose-built to collect, store, and query
|
||||
time series data.
|
||||
{{% product-name %}} is powered by the InfluxDB 3.0 storage engine, that
|
||||
{{% product-name %}} is powered by the InfluxDB 3 storage engine, that
|
||||
provides nearly unlimited series cardinality,
|
||||
improved query performance, and interoperability with widely used data
|
||||
processing tools and platforms.
|
||||
|
@ -109,7 +109,7 @@ The following table compares tools that you can use to interact with
|
|||
| [`influx3` data CLI](#influx3-data-cli){{< req text="\* " color="magenta" >}} | - | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| [InfluxDB HTTP API](#influxdb-http-api){{< req text="\* " color="magenta" >}} | - | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| <span style="opacity:.5;">InfluxDB user interface</span> | - | - | - |
|
||||
| [InfluxDB v3 client libraries](#influxdb-v3-client-libraries){{< req text="\* " color="magenta" >}} | - | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| [InfluxDB 3 client libraries](#influxdb-3-client-libraries){{< req text="\* " color="magenta" >}} | - | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| [InfluxDB v2 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v2/) | - | **{{< icon "check" >}}** | - |
|
||||
| [InfluxDB v1 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v1/) | - | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| [Telegraf](/telegraf/v1/){{< req text="\* " color="magenta" >}} | - | **{{< icon "check" >}}** | - |
|
||||
|
@ -159,7 +159,7 @@ code. The `/api/v2/write` v2-compatible endpoint works with existing InfluxDB
|
|||
InfluxDB client libraries are community-maintained, language-specific clients
|
||||
that interact with InfluxDB APIs.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/)
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/)
|
||||
are the recommended client libraries for writing and querying data
|
||||
{{% product-name %}}. They use the HTTP API to write data and use InfluxDB's
|
||||
Flight gRPC API to query data.
|
||||
|
|
|
@ -48,7 +48,7 @@ section.
|
|||
{{< req type="key" text="Covered in this tutorial" color="magenta" >}}
|
||||
- [`influxctl` CLI](#execute-an-sql-query){{< req text="\* " color="magenta" >}}
|
||||
- [`influx3` data CLI](?t=influx3+CLI#execute-an-sql-query){{< req text="\* " color="magenta" >}}
|
||||
- [InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/){{< req text="\* " color="magenta" >}}
|
||||
- [InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/){{< req text="\* " color="magenta" >}}
|
||||
- [Flight clients](/influxdb3/cloud-dedicated/reference/client-libraries/flight/)
|
||||
- [Superset](/influxdb3/cloud-dedicated/query-data/sql/execute-queries/superset/)
|
||||
- [Grafana](/influxdb3/cloud-dedicated/query-data/sql/execute-queries/grafana/)
|
||||
|
@ -183,7 +183,7 @@ Get started with one of the following tools for querying data stored in an {{% p
|
|||
[`influxctl` CLI](/influxdb3/cloud-dedicated/reference/cli/influxctl/).
|
||||
- **`influx3` CLI**: Query data from your terminal command-line using the
|
||||
Python-based [`influx3` CLI](https://github.com/InfluxCommunity/influxdb3-python).
|
||||
- **InfluxDB v3 client libraries**: Use language-specific (Python, Go, etc.) clients to execute queries in your terminal or custom code.
|
||||
- **InfluxDB 3 client libraries**: Use language-specific (Python, Go, etc.) clients to execute queries in your terminal or custom code.
|
||||
- **Grafana**: Use the [FlightSQL Data Source plugin](https://grafana.com/grafana/plugins/influxdata-flightsql-datasource/), to query, connect, and visualize data.
|
||||
|
||||
For this example, use the following query to select all the data written to the
|
||||
|
@ -306,7 +306,7 @@ configuration file.
|
|||
<!--------------------------- BEGIN influx3 CONTENT --------------------------->
|
||||
{{% influxdb/custom-timestamps %}}
|
||||
|
||||
Query InfluxDB v3 using SQL and the [`influx3` CLI](https://github.com/InfluxCommunity/influxdb3-python-cli).
|
||||
Query InfluxDB 3 using SQL and the [`influx3` CLI](https://github.com/InfluxCommunity/influxdb3-python-cli).
|
||||
|
||||
The following steps include setting up a Python virtual environment already
|
||||
covered in [Get started writing data](/influxdb3/cloud-dedicated/get-started/write/?t=Python#write-line-protocol-to-influxdb).
|
||||
|
@ -1068,7 +1068,7 @@ _This tutorial assumes using Maven version 3.9, Java version >= 15, and an `infl
|
|||
* @throws Exception
|
||||
*/
|
||||
public static void main(final String[] args) throws Exception {
|
||||
// Write data to InfluxDB v3.
|
||||
// Write data to InfluxDB 3.
|
||||
Write.writeLineProtocol();
|
||||
// Run the SQL query.
|
||||
Query.querySQL();
|
||||
|
|
|
@ -792,7 +792,7 @@ the failure message.
|
|||
|
||||
{{% influxdb/custom-timestamps %}}
|
||||
|
||||
To write data to {{% product-name %}} using Go, use the InfluxDB v3
|
||||
To write data to {{% product-name %}} using Go, use the InfluxDB 3
|
||||
[influxdb3-go client library package](https://github.com/InfluxCommunity/influxdb3-go).
|
||||
|
||||
1. Inside of your project directory, create a new module directory and navigate
|
||||
|
@ -1191,7 +1191,7 @@ the failure message.
|
|||
cd influxdb_csharp_client
|
||||
```
|
||||
|
||||
4. Run the following command to install the latest version of the InfluxDB v3
|
||||
4. Run the following command to install the latest version of the InfluxDB 3
|
||||
C# client library.
|
||||
|
||||
<!--pytest.mark.skip-->
|
||||
|
@ -1431,7 +1431,7 @@ _The tutorial assumes using Maven version 3.9 and Java version >= 15._
|
|||
*/
|
||||
public final class Write {
|
||||
/**
|
||||
* Write data to InfluxDB v3.
|
||||
* Write data to InfluxDB 3.
|
||||
*/
|
||||
private Write() {
|
||||
//not called
|
||||
|
@ -1553,7 +1553,7 @@ _The tutorial assumes using Maven version 3.9 and Java version >= 15._
|
|||
* @throws Exception
|
||||
*/
|
||||
public static void main(final String[] args) throws Exception {
|
||||
// Write data to InfluxDB v3.
|
||||
// Write data to InfluxDB 3.
|
||||
Write.writeLineProtocol();
|
||||
}
|
||||
}
|
||||
|
|
|
@ -321,7 +321,7 @@ Replace the following:
|
|||
|
||||
##### Other Telegraf configuration options
|
||||
|
||||
`influx_uint_support`: supported in InfluxDB v3.
|
||||
`influx_uint_support`: supported in InfluxDB 3.
|
||||
|
||||
For more plugin options, see [`influxdb`](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb/README.md) on GitHub.
|
||||
|
||||
|
@ -443,7 +443,7 @@ Replace the following:
|
|||
{{% product-name %}} supports many different tools for querying data, including:
|
||||
|
||||
- [`influx3` data CLI](https://github.com/InfluxCommunity/influxdb3-python-cli)
|
||||
- [InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/)
|
||||
- [InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/)
|
||||
- [Flight clients](/influxdb3/cloud-dedicated/reference/client-libraries/flight/)
|
||||
- [Superset](/influxdb3/cloud-dedicated/query-data/sql/execute-queries/superset/)
|
||||
- [Grafana](/influxdb3/cloud-dedicated/query-data/sql/execute-queries/grafana/)
|
||||
|
|
|
@ -227,7 +227,7 @@ To setup and start using client libraries, see the [Get started](/influxdb3/clou
|
|||
{{% product-name %}} supports many different tools for querying data, including:
|
||||
|
||||
- [`influx3` data CLI](https://github.com/InfluxCommunity/influxdb3-python-cli)
|
||||
- [InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/)
|
||||
- [InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/)
|
||||
- [Flight clients](/influxdb3/cloud-dedicated/reference/client-libraries/flight/)
|
||||
- [Superset](/influxdb3/cloud-dedicated/query-data/sql/execute-queries/superset/)
|
||||
- [Grafana](/influxdb3/cloud-dedicated/query-data/sql/execute-queries/grafana/)
|
||||
|
|
|
@ -37,7 +37,7 @@ The following questions will help guide your decision to migrate.
|
|||
**Yes, you should migrate**. Series cardinality is a major limiting factor with
|
||||
the InfluxDB TSM storage engine. The more unique series in your data, the less
|
||||
performant your database.
|
||||
The InfluxDB v3 storage engine supports limitless series cardinality and is, without
|
||||
The InfluxDB 3 storage engine supports limitless series cardinality and is, without
|
||||
question, the better solution for high series cardinality workloads.
|
||||
|
||||
#### Do you want to use SQL to query your data?
|
||||
|
@ -64,7 +64,7 @@ from the following providers:
|
|||
|
||||
If your deployment requires other cloud providers or regions, you may need to
|
||||
wait until the v3 storage engine is available in a region that meets your requirements.
|
||||
We are currently working to make InfluxDB v3 available on more providers and
|
||||
We are currently working to make InfluxDB 3 available on more providers and
|
||||
in more regions around the world.
|
||||
|
||||
#### Are you reliant on Flux queries and Flux tasks?
|
||||
|
@ -77,7 +77,7 @@ in more regions around the world.
|
|||
|
||||
Before you migrate from InfluxDB 1.x or 2.x to {{< product-name >}}, there
|
||||
are schema design practices supported by the TSM storage engine that are not
|
||||
supported in the InfluxDB v3 storage engine. Specifically, InfluxDB v3 enforces the following schema restrictions:
|
||||
supported in the InfluxDB 3 storage engine. Specifically, InfluxDB 3 enforces the following schema restrictions:
|
||||
|
||||
- You can't use duplicate names for tags and fields.
|
||||
- By default, measurements can contain up to 250 columns where each column
|
||||
|
|
|
@ -38,7 +38,7 @@ the exported data to an InfluxDB Cloud Dedicated database.
|
|||
|
||||
Before you migrate from InfluxDB 1.x to {{< product-name >}}, there
|
||||
are schema design practices supported by the TSM storage engine that are not
|
||||
supported in the InfluxDB v3 storage engine. Specifically, InfluxDB v3 enforces the following schema restrictions:
|
||||
supported in the InfluxDB 3 storage engine. Specifically, InfluxDB 3 enforces the following schema restrictions:
|
||||
|
||||
- You can't use duplicate names for tags and fields.
|
||||
- By default, measurements can contain up to 250 columns where each column
|
||||
|
|
|
@ -3,7 +3,7 @@ title: Migrate data from InfluxDB Cloud to InfluxDB Cloud Dedicated
|
|||
description: >
|
||||
To migrate data from TSM-powered InfluxDB Cloud to InfluxDB Cloud Dedicated
|
||||
powered by the v3 storage engine, query the data in time-based batches and write
|
||||
the queried data to an InfluxDB v3 database in your
|
||||
the queried data to an InfluxDB 3 database in your
|
||||
InfluxDB Cloud Dedicated cluster.
|
||||
menu:
|
||||
influxdb3_cloud_dedicated:
|
||||
|
@ -25,7 +25,7 @@ limits and adjustable quotas, migrate your data in batches.
|
|||
|
||||
The following guide provides instructions for setting up an InfluxDB task
|
||||
that queries data from an InfluxDB Cloud TSM-powered bucket in time-based batches
|
||||
and writes each batch to an {{< product-name >}} (InfluxDB v3) database in
|
||||
and writes each batch to an {{< product-name >}} (InfluxDB 3) database in
|
||||
another organization.
|
||||
|
||||
> [!Important]
|
||||
|
@ -44,7 +44,7 @@ another organization.
|
|||
|
||||
Before you migrate from InfluxDB Cloud (TSM) to {{< product-name >}}, there
|
||||
are schema design practices supported by the TSM storage engine that are not
|
||||
supported in the InfluxDB v3 storage engine. Specifically, InfluxDB v3 enforces the following schema restrictions:
|
||||
supported in the InfluxDB 3 storage engine. Specifically, InfluxDB 3 enforces the following schema restrictions:
|
||||
|
||||
- You can't use duplicate names for tags and fields
|
||||
- By default, measurements can contain up to 250 columns where each column
|
||||
|
|
|
@ -59,13 +59,13 @@ able to evaluate the Cloud Dedicated administrative features directly.
|
|||
|
||||
### Terminology differences
|
||||
|
||||
InfluxDB Cloud Serverless was an upgrade that introduced the InfluxDB 3.0 storage
|
||||
InfluxDB Cloud Serverless was an upgrade that introduced the InfluxDB 3 storage
|
||||
engine to InfluxData’s original InfluxDB Cloud (TSM) multi-tenant solution.
|
||||
InfluxDB Cloud utilizes the Time-Structured Merge Tree (TSM) storage engine in
|
||||
which databases were referred to as "buckets".
|
||||
Cloud Serverless still uses this term.
|
||||
|
||||
InfluxDB Cloud Dedicated has only ever used the InfluxDB 3.0 storage engine.
|
||||
InfluxDB Cloud Dedicated has only ever used the InfluxDB 3 storage engine.
|
||||
Resource names in Cloud Dedicated are more traditionally aligned with SQL database engines.
|
||||
Databases are named "databases" and "measurements" are structured as tables.
|
||||
"Tables" or "measurements" can be used interchangeably.
|
||||
|
@ -110,11 +110,11 @@ platform for InfluxDB Cloud Dedicated.
|
|||
For writing data, InfluxDB Cloud Dedicated and InfluxDB Cloud Serverless both
|
||||
support the v1 API and the v2 write API.
|
||||
|
||||
In addition, [InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/)
|
||||
In addition, [InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/)
|
||||
are available that work the same for both InfluxDB Cloud Serverless and InfluxDB
|
||||
Cloud Dedicated and help avoid any API differences between the two platforms.
|
||||
For more detailed information about choosing a client library, see the
|
||||
_[Choosing a Client Library When Developing with InfluxDB 3.0](https://www.influxdata.com/blog/choosing-client-library-when-developing-with-influxdb-3-0/)_
|
||||
_[Choosing a Client Library When Developing with InfluxDB 3](https://www.influxdata.com/blog/choosing-client-library-when-developing-with-influxdb-3-0/)_
|
||||
blog post.
|
||||
|
||||
### Tasks and alerts differences
|
||||
|
@ -204,7 +204,7 @@ mentioned in _[Tasks and alerts differences](#tasks-and-alerts-differences)_).
|
|||
|
||||
### Use SQL or InfluxQL as your Query Language
|
||||
|
||||
SQL and InfluxQL are optimized for InfluxDB v3 and both are excellent
|
||||
SQL and InfluxQL are optimized for InfluxDB 3 and both are excellent
|
||||
options in Cloud Dedicated and Cloud Serverless.
|
||||
Avoid Flux since it can’t be used with InfluxDB Cloud Dedicated.
|
||||
|
||||
|
|
|
@ -5,5 +5,5 @@ omit_from_sitemap: true
|
|||
---
|
||||
|
||||
This file is used to generate a JSON file containing the navigation structure
|
||||
for this product. The InfluxDB v3 UI retrieves this JSON to build documentation
|
||||
for this product. The InfluxDB 3 UI retrieves this JSON to build documentation
|
||||
links in the UI.
|
||||
|
|
|
@ -16,9 +16,9 @@ Query and downsample time series data stored in InfluxDB and write the
|
|||
downsampled data back to InfluxDB.
|
||||
|
||||
This guide uses [Python](https://www.python.org/) and the
|
||||
[InfluxDB v3 Python client library](https://github.com/InfluxCommunity/influxdb3-python),
|
||||
[InfluxDB 3 Python client library](https://github.com/InfluxCommunity/influxdb3-python),
|
||||
but you can use your runtime of choice and any of the available
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/).
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/).
|
||||
This guide also assumes you have already
|
||||
[setup your Python project and virtual environment](/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/python/#create-a-python-virtual-environment).
|
||||
|
||||
|
|
|
@ -22,9 +22,9 @@ Kafka topic. You can try it locally, with a local Kafka installation, or run it
|
|||
in [Quix Cloud](https://quix.io/) with a free trial.
|
||||
|
||||
This guide uses [Python](https://www.python.org/) and the
|
||||
[InfluxDB v3 Python client library](https://github.com/InfluxCommunity/influxdb3-python),
|
||||
[InfluxDB 3 Python client library](https://github.com/InfluxCommunity/influxdb3-python),
|
||||
but you can use your runtime of choice and any of the available
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/).
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/).
|
||||
This guide also assumes you have already
|
||||
[setup your Python project and virtual environment](/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/python/#create-a-python-virtual-environment).
|
||||
|
||||
|
@ -209,7 +209,7 @@ def get_data():
|
|||
try:
|
||||
myquery = f'SELECT * FROM "{measurement_name}" WHERE time >= {interval}'
|
||||
print(f'sending query {myquery}')
|
||||
# Query InfluxDB 3.0 using influxql or sql
|
||||
# Query InfluxDB 3 using influxql or sql
|
||||
table = influxdb_raw.query(
|
||||
query=myquery,
|
||||
mode='pandas',
|
||||
|
|
|
@ -12,11 +12,11 @@ weight: 104
|
|||
Query, analyze, and send alerts using time series data stored in InfluxDB.
|
||||
|
||||
This guide uses [Python](https://www.python.org/), the
|
||||
[InfluxDB v3 Python client library](https://github.com/InfluxCommunity/influxdb3-python),
|
||||
[InfluxDB 3 Python client library](https://github.com/InfluxCommunity/influxdb3-python),
|
||||
and the [Python Slack SDK](https://slack.dev/python-slack-sdk/) to demonstrate
|
||||
how to query data from InfluxDB and send alerts to Slack, but you can use your
|
||||
runtime and alerting platform of choice with any of the available
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/).
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/).
|
||||
Whatever clients and platforms you choose the use, the process is the same:
|
||||
|
||||
#### Alerting process
|
||||
|
|
|
@ -48,7 +48,7 @@ stored in an {{% product-name %}} database.
|
|||
|
||||
## Install prerequisites
|
||||
|
||||
The examples in this guide assume using a Python virtual environment and the InfluxDB v3 [`influxdb3-python` Python client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/python/).
|
||||
The examples in this guide assume using a Python virtual environment and the InfluxDB 3 [`influxdb3-python` Python client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/python/).
|
||||
For more information, see how to [get started using Python to query InfluxDB](/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/python/).
|
||||
|
||||
Installing `influxdb3-python` also installs the [`pyarrow`](https://arrow.apache.org/docs/python/index.html) library that provides Python bindings for Apache Arrow.
|
||||
|
|
|
@ -51,7 +51,7 @@ and conversion of Arrow format data.
|
|||
|
||||
## Install prerequisites
|
||||
|
||||
The examples in this guide assume using a Python virtual environment and the InfluxDB v3 [`influxdb3-python` Python client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/python/).
|
||||
The examples in this guide assume using a Python virtual environment and the InfluxDB 3 [`influxdb3-python` Python client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/python/).
|
||||
For more information, see how to [get started using Python to query InfluxDB](/influxdb3/cloud-dedicated/query-data/execute-queries/flight-sql/python/).
|
||||
|
||||
Installing `influxdb3-python` also installs the [`pyarrow`](https://arrow.apache.org/docs/python/index.html) library that provides Python bindings for Apache Arrow.
|
||||
|
|
|
@ -123,7 +123,7 @@ To complete [administrative tasks](/influxdb3/cloud-dedicated/admin/), use the
|
|||
|
||||
### Limited InfluxQL feature support
|
||||
|
||||
InfluxQL is being rearchitected to work with the InfluxDB v3 storage engine.
|
||||
InfluxQL is being rearchitected to work with the InfluxDB 3 storage engine.
|
||||
This process is ongoing and some InfluxQL features are still being implemented.
|
||||
For information about the current implementation status of InfluxQL features,
|
||||
see [InfluxQL feature support](/influxdb3/cloud-dedicated/reference/influxql/feature-support/).
|
||||
|
|
|
@ -58,7 +58,7 @@ both InfluxQL and SQL.
|
|||
|
||||
The instructions below are for **Grafana 10.3+** which introduced the newest
|
||||
version of the InfluxDB core plugin.
|
||||
The updated plugin includes **SQL support** for InfluxDB v3-based products such
|
||||
The updated plugin includes **SQL support** for InfluxDB 3-based products such
|
||||
as {{< product-name >}}.
|
||||
{{% /note %}}
|
||||
|
||||
|
|
|
@ -2,8 +2,8 @@
|
|||
title: Use InfluxDB client libraries and SQL or InfluxQL to query data
|
||||
list_title: Use client libraries
|
||||
description: >
|
||||
Use the InfluxDB v3 client libraries with SQL or InfluxQL to query data stored in InfluxDB.
|
||||
InfluxDB v3 client libraries are language-specific packages that integrate with your application.
|
||||
Use the InfluxDB 3 client libraries with SQL or InfluxQL to query data stored in InfluxDB.
|
||||
InfluxDB 3 client libraries are language-specific packages that integrate with your application.
|
||||
Execute queries and retrieve data and metadata over the Flight+gRPC protocol, and then process data using tools in the language of your choice.
|
||||
weight: 30
|
||||
menu:
|
||||
|
@ -15,8 +15,8 @@ related:
|
|||
- /influxdb3/cloud-dedicated/reference/client-libraries/v3/
|
||||
---
|
||||
|
||||
Use the InfluxDB v3 client libraries with SQL or InfluxQL to query data stored in InfluxDB.
|
||||
InfluxDB v3 client libraries are language-specific packages that integrate with your application.
|
||||
Use the InfluxDB 3 client libraries with SQL or InfluxQL to query data stored in InfluxDB.
|
||||
InfluxDB 3 client libraries are language-specific packages that integrate with your application.
|
||||
Execute queries and retrieve data and metadata over the Flight+gRPC protocol, and then process data using tools in the language of your choice.
|
||||
|
||||
{{< children depth="999" description="true" >}}
|
||||
|
|
|
@ -34,7 +34,7 @@ but you can use any HTTP client.
|
|||
{{% warn %}}
|
||||
#### InfluxQL feature support
|
||||
|
||||
InfluxQL is being rearchitected to work with the InfluxDB v3 storage engine.
|
||||
InfluxQL is being rearchitected to work with the InfluxDB 3 storage engine.
|
||||
This process is ongoing and some InfluxQL features are still being implemented.
|
||||
For information about the current implementation status of InfluxQL features,
|
||||
see [InfluxQL feature support](/influxdb3/cloud-dedicated/reference/influxql/feature-support/).
|
||||
|
|
|
@ -40,7 +40,7 @@ The following visualization tools support querying InfluxDB with InfluxQL:
|
|||
{{% warn %}}
|
||||
#### InfluxQL feature support
|
||||
|
||||
InfluxQL is being rearchitected to work with the InfluxDB v3 storage engine.
|
||||
InfluxQL is being rearchitected to work with the InfluxDB 3 storage engine.
|
||||
This process is ongoing and some InfluxQL features are still being implemented.
|
||||
For information about the current implementation status of InfluxQL features,
|
||||
see [InfluxQL feature support](/influxdb3/cloud-dedicated/reference/influxql/feature-support/).
|
||||
|
|
|
@ -52,7 +52,7 @@ For more information on security and query parameterization,
|
|||
see the [OWASP SQL Injection Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.html#defense-option-1-prepared-statements-with-parameterized-queries).
|
||||
{{% /note %}}
|
||||
|
||||
In InfluxDB v3, a parameterized query is an InfluxQL or SQL query that contains one or more named parameter placeholders–variables that represent input data.
|
||||
In InfluxDB 3, a parameterized query is an InfluxQL or SQL query that contains one or more named parameter placeholders–variables that represent input data.
|
||||
|
||||
- [Use parameters in `WHERE` expressions](#use-parameters-in-where-expressions)
|
||||
- [Parameter data types](#parameter-data-types)
|
||||
|
@ -69,7 +69,7 @@ In InfluxDB v3, a parameterized query is an InfluxQL or SQL query that contains
|
|||
|
||||
#### Parameters only supported in `WHERE` expressions
|
||||
|
||||
InfluxDB v3 supports parameters in `WHERE` clause **predicate expressions**.
|
||||
InfluxDB 3 supports parameters in `WHERE` clause **predicate expressions**.
|
||||
Parameter values must be one of the [allowed parameter data types](#parameter-data-types).
|
||||
|
||||
If you use parameters in other expressions or clauses,
|
||||
|
@ -235,7 +235,7 @@ to your {{% product-name %}} database before running the example queries.
|
|||
|
||||
### Use InfluxDB Flight RPC clients
|
||||
|
||||
Using the InfluxDB v3 native Flight RPC protocol and supported clients, you can send a parameterized query and a list of parameter name-value pairs.
|
||||
Using the InfluxDB 3 native Flight RPC protocol and supported clients, you can send a parameterized query and a list of parameter name-value pairs.
|
||||
InfluxDB Flight clients that support parameterized queries pass the parameter name-value pairs in a Flight ticket `params` field.
|
||||
|
||||
The following examples show how to use client libraries to execute parameterized InfluxQL queries:
|
||||
|
@ -341,9 +341,9 @@ func main() {
|
|||
|
||||
## Client support for parameterized queries
|
||||
|
||||
- Not all [InfluxDB v3 Flight clients](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) support parameterized queries.
|
||||
- Not all [InfluxDB 3 Flight clients](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) support parameterized queries.
|
||||
- InfluxDB doesn't currently support parameterized queries or DataFusion prepared statements for Flight SQL or Flight SQL clients.
|
||||
- InfluxDB v3 SQL and InfluxQL parameterized queries aren’t supported in InfluxDB v1 and v2 clients.
|
||||
- InfluxDB 3 SQL and InfluxQL parameterized queries aren’t supported in InfluxDB v1 and v2 clients.
|
||||
|
||||
## Not supported
|
||||
|
||||
|
|
|
@ -49,7 +49,7 @@ For more information on security and query parameterization,
|
|||
see the [OWASP SQL Injection Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.html#defense-option-1-prepared-statements-with-parameterized-queries).
|
||||
{{% /note %}}
|
||||
|
||||
In InfluxDB v3, a parameterized query is an InfluxQL or SQL query that contains one or more named parameter placeholders–variables that represent input data.
|
||||
In InfluxDB 3, a parameterized query is an InfluxQL or SQL query that contains one or more named parameter placeholders–variables that represent input data.
|
||||
|
||||
- [Use parameters in `WHERE` expressions](#use-parameters-in-where-expressions)
|
||||
- [Parameter data types](#parameter-data-types)
|
||||
|
@ -66,7 +66,7 @@ In InfluxDB v3, a parameterized query is an InfluxQL or SQL query that contains
|
|||
|
||||
#### Parameters only supported in `WHERE` expressions
|
||||
|
||||
InfluxDB v3 supports parameters in `WHERE` clause **predicate expressions**.
|
||||
InfluxDB 3 supports parameters in `WHERE` clause **predicate expressions**.
|
||||
Parameter values must be one of the [allowed parameter data types](#parameter-data-types).
|
||||
|
||||
If you use parameters in other expressions or clauses,
|
||||
|
@ -232,7 +232,7 @@ to your {{% product-name %}} database before running the example queries.
|
|||
|
||||
### Use InfluxDB Flight RPC clients
|
||||
|
||||
Using the InfluxDB v3 native Flight RPC protocol and supported clients, you can send a parameterized query and a list of parameter name-value pairs.
|
||||
Using the InfluxDB 3 native Flight RPC protocol and supported clients, you can send a parameterized query and a list of parameter name-value pairs.
|
||||
InfluxDB Flight clients that support parameterized queries pass the parameter name-value pairs in a Flight ticket `params` field.
|
||||
|
||||
The following examples show how to use client libraries to execute parameterized SQL queries:
|
||||
|
@ -333,9 +333,9 @@ func main() {
|
|||
|
||||
## Client support for parameterized queries
|
||||
|
||||
- Not all [InfluxDB v3 Flight clients](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) support parameterized queries.
|
||||
- Not all [InfluxDB 3 Flight clients](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) support parameterized queries.
|
||||
- InfluxDB doesn't currently support parameterized queries or DataFusion prepared statements for Flight SQL or Flight SQL clients.
|
||||
- InfluxDB v3 SQL and InfluxQL parameterized queries aren’t supported in InfluxDB v1 and v2 clients.
|
||||
- InfluxDB 3 SQL and InfluxQL parameterized queries aren’t supported in InfluxDB v1 and v2 clients.
|
||||
|
||||
## Not supported
|
||||
|
||||
|
|
|
@ -19,7 +19,7 @@ related:
|
|||
Learn how to read and analyze a [query plan](/influxdb3/cloud-dedicated/reference/glossary/#query-plan) to
|
||||
understand query execution steps and data organization, and find performance bottlenecks.
|
||||
|
||||
When you query InfluxDB v3, the Querier devises a query plan for executing the query.
|
||||
When you query InfluxDB 3, the Querier devises a query plan for executing the query.
|
||||
The engine tries to determine the optimal plan for the query structure and data.
|
||||
By learning how to generate and interpret reports for the query plan,
|
||||
you can better understand how the query is executed and identify bottlenecks that affect the performance of your query.
|
||||
|
@ -49,7 +49,7 @@ Use the `EXPLAIN` keyword (and the optional [`ANALYZE`](/influxdb3/cloud-dedicat
|
|||
{{% expand-wrapper %}}
|
||||
{{% expand "Use Python and pandas to view an EXPLAIN report" %}}
|
||||
|
||||
The following example shows how to use the InfluxDB v3 Python client library and pandas to view the `EXPLAIN` report for a query:
|
||||
The following example shows how to use the InfluxDB 3 Python client library and pandas to view the `EXPLAIN` report for a query:
|
||||
|
||||
<!-- Import for tests and hide from users.
|
||||
```python
|
||||
|
|
|
@ -107,8 +107,8 @@ See [`InfluxDBClient3.query()` examples](/influxdb3/cloud-dedicated/reference/cl
|
|||
When the Flight client receives a stream, it reads each record batch from the stream until there are no more messages to read.
|
||||
The client considers the request complete when it has received all the messages.
|
||||
|
||||
Flight clients and InfluxDB v3 client libraries provide methods for reading record batches, or "data chunks," from a stream.
|
||||
The InfluxDB v3 Python client library uses the [`pyarrow.flight.FlightStreamReader`](https://arrow.apache.org/docs/python/generated/pyarrow.flight.FlightStreamReader.html#pyarrow.flight.FlightStreamReader) class and provides the following reader methods:
|
||||
Flight clients and InfluxDB 3 client libraries provide methods for reading record batches, or "data chunks," from a stream.
|
||||
The InfluxDB 3 Python client library uses the [`pyarrow.flight.FlightStreamReader`](https://arrow.apache.org/docs/python/generated/pyarrow.flight.FlightStreamReader.html#pyarrow.flight.FlightStreamReader) class and provides the following reader methods:
|
||||
|
||||
- `all`: Read all record batches into a `pyarrow.Table`.
|
||||
- `pandas`: Read all record batches into a `pandas.DataFrame`.
|
||||
|
|
|
@ -51,7 +51,7 @@ The following design strategies generally improve query performance and resource
|
|||
|
||||
#### Include a WHERE clause
|
||||
|
||||
InfluxDB v3 stores data in a Parquet file for each partition.
|
||||
InfluxDB 3 stores data in a Parquet file for each partition.
|
||||
By default, {{< product-name >}} partitions tables by day, but you can also
|
||||
[custom-partition your data](/influxdb3/cloud-dedicated/admin/custom-partitions/).
|
||||
At query time, InfluxDB retrieves files from the Object store to answer a query.
|
||||
|
@ -61,7 +61,7 @@ filters data by a time range or by specific tag values.
|
|||
|
||||
#### SELECT only columns you need
|
||||
|
||||
Because InfluxDB v3 is a columnar database, it only processes the columns
|
||||
Because InfluxDB 3 is a columnar database, it only processes the columns
|
||||
selected in a query, which can mitigate the query performance impact of
|
||||
[wide schemas](/influxdb3/cloud-dedicated/write-data/best-practices/schema-design/#avoid-wide-schemas).
|
||||
|
||||
|
|
|
@ -23,7 +23,7 @@ you can only retrieve system information for that particular instance.
|
|||
|
||||
To get information about queries you've run on the current instance, use SQL to query the [`system.queries` table](/influxdb3/cloud-dedicated/reference/internals/system-tables/#systemqueries-measurement), which contains information from the Querier instance currently handling queries.
|
||||
|
||||
The `system.queries` table is an InfluxDB v3 **debug feature**.
|
||||
The `system.queries` table is an InfluxDB 3 **debug feature**.
|
||||
To enable the feature and query `system.queries`, include an `"iox-debug"` header set to `"true"` and use SQL to query the table--for example:
|
||||
|
||||
|
||||
|
|
|
@ -32,16 +32,16 @@ influxctl [global-flags] [command]
|
|||
|
||||
| Command | Description |
|
||||
| :-------------------------------------------------------------------------- | :------------------------------------- |
|
||||
| [auth](/influxdb3/cloud-dedicated/reference/cli/influxctl/auth/) | Log in to or log out of InfluxDB v3 |
|
||||
| [cluster](/influxdb3/cloud-dedicated/reference/cli/influxctl/cluster/) | List InfluxDB v3 cluster information |
|
||||
| [database](/influxdb3/cloud-dedicated/reference/cli/influxctl/database/) | Manage InfluxDB v3 databases |
|
||||
| [auth](/influxdb3/cloud-dedicated/reference/cli/influxctl/auth/) | Log in to or log out of InfluxDB 3 |
|
||||
| [cluster](/influxdb3/cloud-dedicated/reference/cli/influxctl/cluster/) | List InfluxDB 3 cluster information |
|
||||
| [database](/influxdb3/cloud-dedicated/reference/cli/influxctl/database/) | Manage InfluxDB 3 databases |
|
||||
| [help](/influxdb3/cloud-dedicated/reference/cli/influxctl/help/) | Output `influxctl` help information |
|
||||
| [management](/influxdb3/cloud-dedicated/reference/cli/influxctl/management/) | Manage InfluxDB v3 management tokens |
|
||||
| [query](/influxdb3/cloud-dedicated/reference/cli/influxctl/query/) | Query data from InfluxDB v3 |
|
||||
| [token](/influxdb3/cloud-dedicated/reference/cli/influxctl/token/) | Manage InfluxDB v3 database tokens |
|
||||
| [user](/influxdb3/cloud-dedicated/reference/cli/influxctl/user/) | Manage InfluxDB v3 cluster users |
|
||||
| [management](/influxdb3/cloud-dedicated/reference/cli/influxctl/management/) | Manage InfluxDB 3 management tokens |
|
||||
| [query](/influxdb3/cloud-dedicated/reference/cli/influxctl/query/) | Query data from InfluxDB 3 |
|
||||
| [token](/influxdb3/cloud-dedicated/reference/cli/influxctl/token/) | Manage InfluxDB 3 database tokens |
|
||||
| [user](/influxdb3/cloud-dedicated/reference/cli/influxctl/user/) | Manage InfluxDB 3 cluster users |
|
||||
| [version](/influxdb3/cloud-dedicated/reference/cli/influxctl/version/) | Output the current `influxctl` version |
|
||||
| [write](/influxdb3/cloud-dedicated/reference/cli/influxctl/write/) | Write line protocol to InfluxDB v3 |
|
||||
| [write](/influxdb3/cloud-dedicated/reference/cli/influxctl/write/) | Write line protocol to InfluxDB 3 |
|
||||
|
||||
## Global flags
|
||||
|
||||
|
|
|
@ -87,13 +87,13 @@ _Also see [`influxctl` global flags](/influxdb3/cloud-dedicated/reference/cli/in
|
|||
|
||||
## Examples
|
||||
|
||||
- [Query InfluxDB v3 with SQL](#query-influxdb-v3-with-sql)
|
||||
- [Query InfluxDB v3 with InfluxQL](#query-influxdb-v3-with-influxql)
|
||||
- [Query InfluxDB v3 and return results in table format](#query-influxdb-v3-and-return-results-in-table-format)
|
||||
- [Query InfluxDB v3 and return results in JSON format](#query-influxdb-v3-and-return-results-in-json-format)
|
||||
- [Query InfluxDB v3 and return results with Unix nanosecond timestamps](#query-influxdb-v3-and-return-results-with-unix-nanosecond-timestamps)
|
||||
- [Query InfluxDB v3 using credentials from the connection profile](#query-influxdb-v3-using-credentials-from-the-connection-profile)
|
||||
- [Query data from InfluxDB v3 system tables](#query-data-from-influxdb-v3-system-tables)
|
||||
- [Query InfluxDB 3 with SQL](#query-influxdb-3-with-sql)
|
||||
- [Query InfluxDB 3 with InfluxQL](#query-influxdb-3-with-influxql)
|
||||
- [Query InfluxDB 3 and return results in table format](#query-influxdb-3-and-return-results-in-table-format)
|
||||
- [Query InfluxDB 3 and return results in JSON format](#query-influxdb-3-and-return-results-in-json-format)
|
||||
- [Query InfluxDB 3 and return results with Unix nanosecond timestamps](#query-influxdb-3-and-return-results-with-unix-nanosecond-timestamps)
|
||||
- [Query InfluxDB 3 using credentials from the connection profile](#query-influxdb-3-using-credentials-from-the-connection-profile)
|
||||
- [Query data from InfluxDB 3 system tables](#query-data-from-influxdb-3-system-tables)
|
||||
|
||||
In the examples below, replace the following:
|
||||
|
||||
|
@ -102,7 +102,7 @@ In the examples below, replace the following:
|
|||
- {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}:
|
||||
Name of the database to query
|
||||
|
||||
### Query InfluxDB v3 with SQL
|
||||
### Query InfluxDB 3 with SQL
|
||||
|
||||
{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
|
||||
|
||||
|
@ -142,7 +142,7 @@ cat ./query.sql | influxctl query \
|
|||
|
||||
{{% /code-placeholders %}}
|
||||
|
||||
### Query InfluxDB v3 with InfluxQL
|
||||
### Query InfluxDB 3 with InfluxQL
|
||||
|
||||
{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
|
||||
|
||||
|
@ -185,7 +185,7 @@ cat ./query.influxql | influxctl query \
|
|||
|
||||
{{% /code-placeholders %}}
|
||||
|
||||
### Query InfluxDB v3 and return results in table format
|
||||
### Query InfluxDB 3 and return results in table format
|
||||
|
||||
{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
|
||||
|
||||
|
@ -245,7 +245,7 @@ cat ./query.sql | influxctl query \
|
|||
{{% /expand %}}
|
||||
{{< /expand-wrapper >}}
|
||||
|
||||
### Query InfluxDB v3 and return results in JSON format
|
||||
### Query InfluxDB 3 and return results in JSON format
|
||||
|
||||
{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
|
||||
|
||||
|
@ -334,7 +334,7 @@ cat ./query.sql | influxctl query \
|
|||
{{% /expand %}}
|
||||
{{< /expand-wrapper >}}
|
||||
|
||||
### Query InfluxDB v3 and return results with Unix nanosecond timestamps
|
||||
### Query InfluxDB 3 and return results with Unix nanosecond timestamps
|
||||
|
||||
{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
|
||||
|
||||
|
@ -397,7 +397,7 @@ cat ./query.sql | influxctl query \
|
|||
{{% /expand %}}
|
||||
{{< /expand-wrapper >}}
|
||||
|
||||
### Query InfluxDB v3 using credentials from the connection profile
|
||||
### Query InfluxDB 3 using credentials from the connection profile
|
||||
|
||||
The following example uses the `database` and `token` defined in the `default`
|
||||
[connection profile](/influxdb3/cloud-dedicated/reference/cli/influxctl/#configure-connection-profiles).
|
||||
|
@ -408,10 +408,10 @@ influxctl query "SELECT * FROM home WHERE time >= '2022-01-01T08:00:00Z'"
|
|||
```
|
||||
{{% /influxdb/custom-timestamps %}}
|
||||
|
||||
### Query data from InfluxDB v3 system tables
|
||||
### Query data from InfluxDB 3 system tables
|
||||
|
||||
{{% note %}}
|
||||
You must use **SQL** to query InfluxDB v3 system tables.
|
||||
You must use **SQL** to query InfluxDB 3 system tables.
|
||||
{{% /note %}}
|
||||
|
||||
{{% warn %}}
|
||||
|
@ -472,7 +472,7 @@ cat ./query.sql | influxctl query \
|
|||
|
||||
- Add InfluxQL support and introduce the `--language` flag to specify the query
|
||||
language.
|
||||
- Add `--enable-system-tables` flag to enable the ability to query InfluxDB v3
|
||||
- Add `--enable-system-tables` flag to enable the ability to query InfluxDB 3
|
||||
system tables.
|
||||
|
||||
{{% /expand %}}
|
||||
|
|
|
@ -70,10 +70,10 @@ _Also see [`influxctl` global flags](/influxdb3/cloud-dedicated/reference/cli/in
|
|||
|
||||
## Examples
|
||||
|
||||
- [Write line protocol to InfluxDB v3](#write-line-protocol-to-influxdb-v3)
|
||||
- [Write line protocol to InfluxDB v3 with non-default timestamp precision](#write-line-protocol-to-influxdb-v3-with-non-default-timestamp-precision)
|
||||
- [Write line protocol to InfluxDB v3 with a custom batch size](#write-line-protocol-to-influxdb-v3-with-a-custom-batch-size)
|
||||
- [Write line protocol to InfluxDB v3 using credentials from the connection profile](#write-line-protocol-to-influxdb-v3-using-credentials-from-the-connection-profile)
|
||||
- [Write line protocol to InfluxDB 3](#write-line-protocol-to-influxdb-3)
|
||||
- [Write line protocol to InfluxDB 3 with non-default timestamp precision](#write-line-protocol-to-influxdb-3-with-non-default-timestamp-precision)
|
||||
- [Write line protocol to InfluxDB 3 with a custom batch size](#write-line-protocol-to-influxdb-3-with-a-custom-batch-size)
|
||||
- [Write line protocol to InfluxDB 3 using credentials from the connection profile](#write-line-protocol-to-influxdb-3-using-credentials-from-the-connection-profile)
|
||||
|
||||
In the examples below, replace the following:
|
||||
|
||||
|
@ -82,7 +82,7 @@ In the examples below, replace the following:
|
|||
- {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}:
|
||||
Name of the database to write to
|
||||
|
||||
### Write line protocol to InfluxDB v3
|
||||
### Write line protocol to InfluxDB 3
|
||||
|
||||
{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
|
||||
|
||||
|
@ -126,7 +126,7 @@ cat ./metrics.lp | influxctl write \
|
|||
|
||||
{{% /code-placeholders %}}
|
||||
|
||||
### Write line protocol to InfluxDB v3 with non-default timestamp precision
|
||||
### Write line protocol to InfluxDB 3 with non-default timestamp precision
|
||||
|
||||
{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
|
||||
|
||||
|
@ -173,7 +173,7 @@ cat ./metrics.lp | influxctl write \
|
|||
|
||||
{{% /code-placeholders %}}
|
||||
|
||||
### Write line protocol to InfluxDB v3 with a custom batch size
|
||||
### Write line protocol to InfluxDB 3 with a custom batch size
|
||||
|
||||
{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
|
||||
|
||||
|
@ -220,7 +220,7 @@ cat ./metrics.lp | influxctl write \
|
|||
|
||||
{{% /code-placeholders %}}
|
||||
|
||||
### Write line protocol to InfluxDB v3 with a custom client timeout
|
||||
### Write line protocol to InfluxDB 3 with a custom client timeout
|
||||
|
||||
{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
|
||||
|
||||
|
@ -267,7 +267,7 @@ cat ./metrics.lp | influxctl write \
|
|||
|
||||
{{% /code-placeholders %}}
|
||||
|
||||
### Write line protocol to InfluxDB v3 using credentials from the connection profile
|
||||
### Write line protocol to InfluxDB 3 using credentials from the connection profile
|
||||
|
||||
The following example uses the `database` and `token` defined in the `default`
|
||||
[connection profile](/influxdb3/cloud-dedicated/reference/cli/influxctl/#configure-connection-profiles).
|
||||
|
|
|
@ -19,15 +19,15 @@ Flight RPC and Flight SQL clients are language-specific drivers that interact wi
|
|||
Apache Arrow Flight RPC and Flight SQL protocols define APIs for servers and clients.
|
||||
|
||||
{{% note %}}
|
||||
#### Use InfluxDB v3 client libraries
|
||||
#### Use InfluxDB 3 client libraries
|
||||
|
||||
We recommend using [InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) for integrating InfluxDB v3 with your application code.
|
||||
We recommend using [InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) for integrating InfluxDB 3 with your application code.
|
||||
Client libraries wrap Apache Arrow Flight clients
|
||||
and provide convenient methods for [writing](/influxdb3/cloud-dedicated/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/cloud-dedicated/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
||||
{{% /note %}}
|
||||
|
||||
**Flight RPC clients** can use SQL or InfluxQL to query data stored in an {{% product-name %}} database.
|
||||
Using InfluxDB v3's IOx-specific Flight RPC protocol, clients send a single `DoGet()` request to authenticate, query, and retrieve data.
|
||||
Using InfluxDB 3's IOx-specific Flight RPC protocol, clients send a single `DoGet()` request to authenticate, query, and retrieve data.
|
||||
|
||||
**Flight SQL clients** use the [Flight SQL protocol](https://arrow.apache.org/docs/format/FlightSql.html) for querying an SQL database server.
|
||||
They can use SQL to query data stored in an {{% product-name %}} database, but they can't use InfuxQL.
|
||||
|
|
|
@ -17,11 +17,11 @@ weight: 201
|
|||
For more information, see the [C# client example on GitHub](https://github.com/apache/arrow/tree/main/csharp/examples/FlightClientExample).
|
||||
|
||||
{{% note %}}
|
||||
#### Use InfluxDB v3 client libraries
|
||||
#### Use InfluxDB 3 client libraries
|
||||
|
||||
We recommend using the [`influxdb3-csharp` C# client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/csharp/) for integrating InfluxDB v3 with your C# application code.
|
||||
We recommend using the [`influxdb3-csharp` C# client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/csharp/) for integrating InfluxDB 3 with your C# application code.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
and provide convenient methods for [writing](/influxdb3/cloud-dedicated/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/cloud-dedicated/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
||||
Client libraries can query using SQL or InfluxQL.
|
||||
{{% /note %}}
|
||||
|
|
|
@ -17,11 +17,11 @@ weight: 201
|
|||
[Apache Arrow for Go](https://pkg.go.dev/github.com/apache/arrow/go/v12) integrates with Go scripts and applications to query data stored in InfluxDB.
|
||||
|
||||
{{% note %}}
|
||||
#### Use InfluxDB v3 client libraries
|
||||
#### Use InfluxDB 3 client libraries
|
||||
|
||||
We recommend using the [`influxdb3-go` Go client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/go/) for integrating InfluxDB v3 with your Go application code.
|
||||
We recommend using the [`influxdb3-go` Go client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/go/) for integrating InfluxDB 3 with your Go application code.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
and provide convenient methods for [writing](/influxdb3/cloud-dedicated/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/cloud-dedicated/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
||||
Client libraries can query using SQL or InfluxQL.
|
||||
{{% /note %}}
|
||||
|
|
|
@ -42,11 +42,11 @@ list_code_example: |
|
|||
[Apache Arrow Flight SQL for Java](https://arrow.apache.org/docs/java/reference/org/apache/arrow/flight/sql/package-summary.html) integrates with Java applications to query and retrieve data from Flight database servers using RPC and SQL.
|
||||
|
||||
{{% note %}}
|
||||
#### Use InfluxDB v3 client libraries
|
||||
#### Use InfluxDB 3 client libraries
|
||||
|
||||
We recommend using the [`influxdb3-java` Java client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/java/) for integrating InfluxDB v3 with your Java application code.
|
||||
We recommend using the [`influxdb3-java` Java client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/java/) for integrating InfluxDB 3 with your Java application code.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
and provide convenient methods for [writing](/influxdb3/cloud-dedicated/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/cloud-dedicated/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
||||
Client libraries can query using SQL or InfluxQL.
|
||||
{{% /note %}}
|
||||
|
@ -68,7 +68,7 @@ Client libraries can query using SQL or InfluxQL.
|
|||
Write a Java class for a Flight SQL client that connects to {{% product-name %}},
|
||||
executes an SQL query, and retrieves data stored in an {{% product-name %}} database.
|
||||
|
||||
The example uses the [Apache Arrow Java implementation (`org.apache.arrow`)](https://arrow.apache.org/docs/java/index.html) for interacting with Flight database servers like InfluxDB v3.
|
||||
The example uses the [Apache Arrow Java implementation (`org.apache.arrow`)](https://arrow.apache.org/docs/java/index.html) for interacting with Flight database servers like InfluxDB 3.
|
||||
|
||||
- **`org.apache.arrow`**: Provides classes and methods for integrating Java applications with Apache Arrow data and protocols.
|
||||
- **`org.apache.arrow.flight.sql`**: Provides classes and methods for
|
||||
|
|
|
@ -50,11 +50,11 @@ list_code_example: |
|
|||
[Apache Arrow Python bindings](https://arrow.apache.org/docs/python/index.html) integrate with Python scripts and applications to query data stored in InfluxDB.
|
||||
|
||||
{{% note %}}
|
||||
#### Use InfluxDB v3 client libraries
|
||||
#### Use InfluxDB 3 client libraries
|
||||
|
||||
We recommend using the [`influxdb3-python` Python client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/python/) for integrating InfluxDB v3 with your Python application code.
|
||||
We recommend using the [`influxdb3-python` Python client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/python/) for integrating InfluxDB 3 with your Python application code.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
and provide convenient methods for [writing](/influxdb3/cloud-dedicated/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/cloud-dedicated/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
||||
Client libraries can query using SQL or InfluxQL.
|
||||
{{% /note %}}
|
||||
|
|
|
@ -15,11 +15,11 @@ aliases:
|
|||
The [Python `flightsql-dbapi` Flight SQL DBAPI library](https://github.com/influxdata/flightsql-dbapi) integrates with Python applications using SQL to query data stored in an {{% product-name %}} database. The `flightsql-dbapi` library uses the [Flight SQL protocol](https://arrow.apache.org/docs/format/FlightSql.html) to query and retrieve data.
|
||||
|
||||
{{% note %}}
|
||||
#### Use InfluxDB v3 client libraries
|
||||
#### Use InfluxDB 3 client libraries
|
||||
|
||||
We recommend using the [`influxdb3-python` Python client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/python/) for integrating InfluxDB v3 with your Python application code.
|
||||
We recommend using the [`influxdb3-python` Python client library](/influxdb3/cloud-dedicated/reference/client-libraries/v3/python/) for integrating InfluxDB 3 with your Python application code.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) wrap Apache Arrow Flight clients
|
||||
and provide convenient methods for [writing](/influxdb3/cloud-dedicated/get-started/write/#write-line-protocol-to-influxdb), [querying](/influxdb3/cloud-dedicated/get-started/query/#execute-an-sql-query), and processing data stored in {{% product-name %}}.
|
||||
Client libraries can query using SQL or InfluxQL.
|
||||
{{% /note %}}
|
||||
|
|
|
@ -15,7 +15,7 @@ InfluxDB client libraries are language-specific tools that integrate with Influx
|
|||
Client libraries for InfluxDB v1 work with the InfluxDB 1.7 API and should be fully compatible with InfluxDB 1.5+.
|
||||
|
||||
{{% note %}}
|
||||
Upgrade to InfluxDB v3 to use new client libraries compatible with InfluxDB write APIs, SQL, and InfluxQL. For more information, see [InfluxDB client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/).
|
||||
Upgrade to InfluxDB 3 to use new client libraries compatible with InfluxDB write APIs, SQL, and InfluxQL. For more information, see [InfluxDB client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/).
|
||||
{{% /note %}}
|
||||
|
||||
Functionality varies among client libraries.
|
||||
|
|
|
@ -12,13 +12,13 @@ influxdb3/cloud-dedicated/tags: [client libraries, API, developer tools]
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -13,13 +13,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -16,13 +16,13 @@ aliases:
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -19,13 +19,13 @@ related:
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -16,13 +16,13 @@ aliases:
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -13,13 +13,13 @@ aliases:
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -16,13 +16,13 @@ related:
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -17,13 +17,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -12,13 +12,13 @@ weight: 201
|
|||
prepend:
|
||||
block: warn
|
||||
content: |
|
||||
### Use InfluxDB v3 clients
|
||||
### Use InfluxDB 3 clients
|
||||
|
||||
The `/api/v2/query` API endpoint and associated tooling, such as InfluxDB v2 client libraries and the `influx` CLI, **can't** query an {{% product-name omit=" Clustered" %}} cluster.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-dedicated/reference/client-libraries/v3/) and [Flight SQL clients](/influxdb3/cloud-dedicated/reference/client-libraries/) are available that integrate with your code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB v3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
InfluxDB 3 supports many different tools for [**writing**](/influxdb3/cloud-dedicated/write-data/) and [**querying**](/influxdb3/cloud-dedicated/query-data/) data.
|
||||
[**Compare tools you can use**](/influxdb3/cloud-dedicated/get-started/#tools-to-use) to interact with {{% product-name %}}.
|
||||
---
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: InfluxDB v3 API client libraries
|
||||
title: InfluxDB 3 API client libraries
|
||||
description: >
|
||||
InfluxDB v3 client libraries use InfluxDB HTTP APIs to write data and use [Flight clients](/influxdb3/cloud-dedicated/reference/client-libraries/flight-sql) to execute SQL and InfluxQL queries.
|
||||
InfluxDB 3 client libraries use InfluxDB HTTP APIs to write data and use [Flight clients](/influxdb3/cloud-dedicated/reference/client-libraries/flight-sql) to execute SQL and InfluxQL queries.
|
||||
View the list of available client libraries.
|
||||
weight: 30
|
||||
menu:
|
||||
|
@ -11,9 +11,9 @@ menu:
|
|||
influxdb3/cloud-dedicated/tags: [client libraries, API, developer tools]
|
||||
---
|
||||
|
||||
## Client libraries for InfluxDB v3
|
||||
## Client libraries for InfluxDB 3
|
||||
|
||||
InfluxDB v3 client libraries are language-specific packages that work with
|
||||
InfluxDB 3 client libraries are language-specific packages that work with
|
||||
and integrate with your application to write to and query data in {{% product-name %}}.
|
||||
InfluxData and the user community maintain client libraries for developers who want to take advantage of:
|
||||
|
||||
|
@ -25,13 +25,13 @@ InfluxDB client libraries provide configurable batch writing of data to InfluxDB
|
|||
They can be used to construct line protocol data and transform data from other formats
|
||||
to line protocol.
|
||||
|
||||
InfluxDB v3 client libraries can query InfluxDB v3 using InfluxDB v3's IOx-specific Arrow Flight protocol with gRPC.
|
||||
InfluxDB 3 client libraries can query InfluxDB 3 using InfluxDB 3's IOx-specific Arrow Flight protocol with gRPC.
|
||||
Client libraries use Flight clients to execute SQL and InfluxQL queries, request
|
||||
database information, and retrieve data stored in {{% product-name %}}.
|
||||
|
||||
Additional features may vary among client libraries.
|
||||
|
||||
For specifics about a client library, see the library's GitHub repository.
|
||||
InfluxDB v3 client libraries are part of the [Influx Community](https://github.com/InfluxCommunity).
|
||||
InfluxDB 3 client libraries are part of the [Influx Community](https://github.com/InfluxCommunity).
|
||||
|
||||
{{< children depth="999" description="true" >}}
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: C# .NET client library for InfluxDB v3
|
||||
title: C# .NET client library for InfluxDB 3
|
||||
list_title: C# .NET
|
||||
description: >
|
||||
The InfluxDB v3 `influxdb3-csharp` C# .NET client library integrates with C# .NET scripts and applications to write and query data stored in an InfluxDB Cloud Dedicated database.
|
||||
The InfluxDB 3 `influxdb3-csharp` C# .NET client library integrates with C# .NET scripts and applications to write and query data stored in an InfluxDB Cloud Dedicated database.
|
||||
external_url: https://github.com/InfluxCommunity/influxdb3-csharp
|
||||
menu:
|
||||
influxdb3_cloud_dedicated:
|
||||
|
@ -13,9 +13,9 @@ influxdb3/cloud-dedicated/tags: [C#, gRPC, SQL, Flight SQL, client libraries]
|
|||
weight: 201
|
||||
---
|
||||
|
||||
The InfluxDB v3 [`influxdb3-csharp` C# .NET client library](https://github.com/InfluxCommunity/influxdb3-csharp) integrates with C# .NET scripts and applications
|
||||
The InfluxDB 3 [`influxdb3-csharp` C# .NET client library](https://github.com/InfluxCommunity/influxdb3-csharp) integrates with C# .NET scripts and applications
|
||||
to write and query data stored in an {{% product-name %}} database.
|
||||
|
||||
The documentation for this client library is available on GitHub.
|
||||
|
||||
<a href="https://github.com/InfluxCommunity/influxdb3-csharp" target="_blank" class="btn github">InfluxDB v3 C# .NET client library</a>
|
||||
<a href="https://github.com/InfluxCommunity/influxdb3-csharp" target="_blank" class="btn github">InfluxDB 3 C# .NET client library</a>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Go client library for InfluxDB v3
|
||||
title: Go client library for InfluxDB 3
|
||||
list_title: Go
|
||||
description: The InfluxDB v3 `influxdb3-go` Go client library integrates with Go scripts and applications to write and query data stored in an {{% product-name %}} database.
|
||||
description: The InfluxDB 3 `influxdb3-go` Go client library integrates with Go scripts and applications to write and query data stored in an {{% product-name %}} database.
|
||||
menu:
|
||||
influxdb3_cloud_dedicated:
|
||||
name: Go
|
||||
|
@ -14,7 +14,7 @@ aliases:
|
|||
- /influxdb3/cloud-dedicated/tools/client-libraries/go/
|
||||
---
|
||||
|
||||
The InfluxDB v3 [`influxdb3-go` Go client library](https://github.com/InfluxCommunity/influxdb3-go) integrates with Go scripts and applications
|
||||
The InfluxDB 3 [`influxdb3-go` Go client library](https://github.com/InfluxCommunity/influxdb3-go) integrates with Go scripts and applications
|
||||
to write and query data stored in an {{% product-name %}} database.
|
||||
|
||||
## Installation
|
||||
|
@ -110,7 +110,7 @@ Replace the following configuration values:
|
|||
|
||||
### Function `Client.Query()`
|
||||
|
||||
Query data from InfluxDB v3 using SQL.
|
||||
Query data from InfluxDB 3 using SQL.
|
||||
|
||||
#### Syntax
|
||||
|
||||
|
@ -145,7 +145,7 @@ iterator, err := client.Query(context.Background(), query)
|
|||
|
||||
### Function `Client.QueryWithOptions()`
|
||||
|
||||
Query data from InfluxDB v3 with query options such as **query type** for querying with InfluxQL.
|
||||
Query data from InfluxDB 3 with query options such as **query type** for querying with InfluxQL.
|
||||
|
||||
#### Syntax
|
||||
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: Java client library for InfluxDB v3
|
||||
title: Java client library for InfluxDB 3
|
||||
list_title: Java
|
||||
description: >
|
||||
The InfluxDB v3 `influxdb3-java` Java client library integrates with application code to write and query data stored in an InfluxDB Cloud Dedicated database.
|
||||
The InfluxDB 3 `influxdb3-java` Java client library integrates with application code to write and query data stored in an InfluxDB Cloud Dedicated database.
|
||||
menu:
|
||||
influxdb3_cloud_dedicated:
|
||||
name: Java
|
||||
|
@ -12,16 +12,16 @@ influxdb3/cloud-dedicated/tags: [Flight client, Java, gRPC, SQL, Flight SQL, cli
|
|||
weight: 201
|
||||
---
|
||||
|
||||
The InfluxDB v3 [`influxdb3-java` Java client library](https://github.com/InfluxCommunity/influxdb3-java) integrates
|
||||
The InfluxDB 3 [`influxdb3-java` Java client library](https://github.com/InfluxCommunity/influxdb3-java) integrates
|
||||
with Java application code to write and query data stored in {{% product-name %}}.
|
||||
|
||||
InfluxDB client libraries provide configurable batch writing of data to {{% product-name %}}.
|
||||
Use client libraries to construct line protocol data, transform data from other formats
|
||||
to line protocol, and batch write line protocol data to InfluxDB HTTP APIs.
|
||||
|
||||
InfluxDB v3 client libraries can query {{% product-name %}} using SQL or InfluxQL.
|
||||
InfluxDB 3 client libraries can query {{% product-name %}} using SQL or InfluxQL.
|
||||
The `influxdb3-java` Java client library wraps the Apache Arrow `org.apache.arrow.flight.FlightClient`
|
||||
in a convenient InfluxDB v3 interface for executing SQL and InfluxQL queries, requesting
|
||||
in a convenient InfluxDB 3 interface for executing SQL and InfluxQL queries, requesting
|
||||
server metadata, and retrieving data from {{% product-name %}} using the Flight protocol with gRPC.
|
||||
|
||||
- [Installation](#installation)
|
||||
|
@ -358,4 +358,4 @@ To query data and process the results:
|
|||
}
|
||||
```
|
||||
|
||||
<a class="btn" href="https://github.com/InfluxCommunity/influxdb3-java/" target="\_blank">View the InfluxDB v3 Java client library</a>
|
||||
<a class="btn" href="https://github.com/InfluxCommunity/influxdb3-java/" target="\_blank">View the InfluxDB 3 Java client library</a>
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: JavaScript client library for InfluxDB v3
|
||||
title: JavaScript client library for InfluxDB 3
|
||||
list_title: JavaScript
|
||||
description: >
|
||||
The InfluxDB v3 `influxdb3-js` JavaScript client library integrates with JavaScript scripts and applications to write and query data stored in an InfluxDB Cloud Dedicated database.
|
||||
The InfluxDB 3 `influxdb3-js` JavaScript client library integrates with JavaScript scripts and applications to write and query data stored in an InfluxDB Cloud Dedicated database.
|
||||
external_url: https://github.com/InfluxCommunity/influxdb3-js
|
||||
menu:
|
||||
influxdb3_cloud_dedicated:
|
||||
|
@ -16,9 +16,9 @@ aliases:
|
|||
- /influxdb3/cloud-dedicated/tools/client-libraries/go/
|
||||
---
|
||||
|
||||
The InfluxDB v3 [`influxdb3-js` JavaScript client library](https://github.com/InfluxCommunity/influxdb3-js) integrates with JavaScript scripts and applications
|
||||
The InfluxDB 3 [`influxdb3-js` JavaScript client library](https://github.com/InfluxCommunity/influxdb3-js) integrates with JavaScript scripts and applications
|
||||
to write and query data stored in an {{% product-name %}} database.
|
||||
|
||||
The documentation for this client library is available on GitHub.
|
||||
|
||||
<a href="https://github.com/InfluxCommunity/influxdb3-js" target="_blank" class="btn github">InfluxDB v3 JavaScript client library</a>
|
||||
<a href="https://github.com/InfluxCommunity/influxdb3-js" target="_blank" class="btn github">InfluxDB 3 JavaScript client library</a>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Python client library for InfluxDB v3
|
||||
title: Python client library for InfluxDB 3
|
||||
list_title: Python
|
||||
description: The InfluxDB v3 `influxdb3-python` Python client library integrates with Python scripts and applications to write and query data stored in an InfluxDB Cloud Dedicated database.
|
||||
description: The InfluxDB 3 `influxdb3-python` Python client library integrates with Python scripts and applications to write and query data stored in an InfluxDB Cloud Dedicated database.
|
||||
menu:
|
||||
influxdb3_cloud_dedicated:
|
||||
name: Python
|
||||
|
@ -49,16 +49,16 @@ list_code_example: |
|
|||
```
|
||||
---
|
||||
|
||||
The InfluxDB v3 [`influxdb3-python` Python client library](https://github.com/InfluxCommunity/influxdb3-python)
|
||||
The InfluxDB 3 [`influxdb3-python` Python client library](https://github.com/InfluxCommunity/influxdb3-python)
|
||||
integrates {{% product-name %}} write and query operations with Python scripts and applications.
|
||||
|
||||
InfluxDB client libraries provide configurable batch writing of data to {{% product-name %}}.
|
||||
Client libraries can be used to construct line protocol data, transform data from other formats
|
||||
to line protocol, and batch write line protocol data to InfluxDB HTTP APIs.
|
||||
|
||||
InfluxDB v3 client libraries can query {{% product-name %}} using SQL or InfluxQL.
|
||||
InfluxDB 3 client libraries can query {{% product-name %}} using SQL or InfluxQL.
|
||||
The `influxdb3-python` Python client library wraps the Apache Arrow `pyarrow.flight` client
|
||||
in a convenient InfluxDB v3 interface for executing SQL and InfluxQL queries, requesting
|
||||
in a convenient InfluxDB 3 interface for executing SQL and InfluxQL queries, requesting
|
||||
server metadata, and retrieving data from {{% product-name %}} using the Flight protocol with gRPC.
|
||||
|
||||
{{% note %}}
|
||||
|
|
|
@ -124,7 +124,7 @@ CSV file format is not fully standardized.
|
|||
|
||||
Cardinality is the number of unique values in a set.
|
||||
Series cardinality is the number of unique [series](#series) in a database as a whole.
|
||||
With the InfluxDB v3 storage engine, high series cardinality _does not_ affect performance.
|
||||
With the InfluxDB 3 storage engine, high series cardinality _does not_ affect performance.
|
||||
|
||||
### cluster
|
||||
|
||||
|
@ -460,7 +460,7 @@ Related entries:
|
|||
|
||||
### IOx
|
||||
|
||||
The IOx storage engine (InfluxDB v3 storage engine) is a real-time, columnar
|
||||
The IOx storage engine (InfluxDB 3 storage engine) is a real-time, columnar
|
||||
database optimized for time series data built in Rust on top of
|
||||
[Apache Arrow](https://arrow.apache.org/) and
|
||||
[DataFusion](https://arrow.apache.org/datafusion/user-guide/introduction.html).
|
||||
|
@ -1048,7 +1048,7 @@ Related entries: [aggregate](#aggregate), [function](#function), [selector](#sel
|
|||
|
||||
The InfluxDB v1 and v2 data storage format that allows greater compaction and
|
||||
higher write and read throughput than B+ or LSM tree implementations.
|
||||
The TSM storage engine has been replaced by the [InfluxDB v3 storage engine (IOx)](#iox).
|
||||
The TSM storage engine has been replaced by the [InfluxDB 3 storage engine (IOx)](#iox).
|
||||
|
||||
Related entries:
|
||||
[IOx](#iox)
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: InfluxQL feature support
|
||||
description: >
|
||||
InfluxQL is being rearchitected to work with the InfluxDB 3.0 storage engine.
|
||||
InfluxQL is being rearchitected to work with the InfluxDB 3 storage engine.
|
||||
This process is ongoing and some InfluxQL features are still being implemented.
|
||||
This page provides information about the current implementation status of
|
||||
InfluxQL features.
|
||||
|
|
|
@ -17,7 +17,7 @@ related:
|
|||
- /influxdb3/cloud-dedicated/reference/internals/storage-engine/
|
||||
---
|
||||
|
||||
A query plan is a sequence of steps that the InfluxDB v3 [Querier](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#querier) devises and executes to calculate the result of a query.
|
||||
A query plan is a sequence of steps that the InfluxDB 3 [Querier](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#querier) devises and executes to calculate the result of a query.
|
||||
The Querier uses DataFusion and Arrow to build and execute query plans
|
||||
that call DataFusion and InfluxDB-specific operators that read data from the [Object store](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#object-store), and the [Ingester](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#ingester), and apply query transformations, such as deduplicating, filtering, aggregating, merging, projecting, and sorting to calculate the final result.
|
||||
|
||||
|
@ -188,7 +188,7 @@ Files are referenced by path:
|
|||
- `1/1/b862a7e9b.../243db601-....parquet`
|
||||
- `1/1/b862a7e9b.../f5fb7c7d-....parquet`
|
||||
|
||||
In InfluxDB v3, the path structure represents how data is organized.
|
||||
In InfluxDB 3, the path structure represents how data is organized.
|
||||
|
||||
A path has the following structure:
|
||||
|
||||
|
@ -300,7 +300,7 @@ DataFusion [`ProjectionExec`](https://docs.rs/datafusion/latest/datafusion/physi
|
|||
|
||||
### `RecordBatchesExec`
|
||||
|
||||
The InfluxDB `RecordBatchesExec` implementation retrieves and scans recently written, yet-to-be-persisted, data from the InfluxDB v3 [Ingester](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#ingester).
|
||||
The InfluxDB `RecordBatchesExec` implementation retrieves and scans recently written, yet-to-be-persisted, data from the InfluxDB 3 [Ingester](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#ingester).
|
||||
|
||||
When generating the plan, the [Querier](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#querier) sends the query criteria, such as database, table, and columns, to the [Ingester](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#ingester) to retrieve data not yet persisted to Parquet files.
|
||||
If the [Ingester](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#ingester) has data that meets the criteria (the chunk size is non-zero), then the plan includes `RecordBatchesExec`.
|
||||
|
@ -379,14 +379,14 @@ For example, the following chunks represent line protocol written to InfluxDB:
|
|||
If data overlaps at query time, the [Querier](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#querier) must include the _deduplication_ process in the query plan, which uses the same multi-column sort-merge operators used by the [Ingester](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#ingester).
|
||||
Compared to an ingestion plan that uses sort-merge operators, a query plan is more complex and ensures that data streams through the plan after deduplication.
|
||||
|
||||
Because sort-merge operations used in deduplication have a non-trivial execution cost, InfluxDB v3 tries to avoid the need for deduplication.
|
||||
Because sort-merge operations used in deduplication have a non-trivial execution cost, InfluxDB 3 tries to avoid the need for deduplication.
|
||||
Due to how InfluxDB organizes data, a Parquet file never contains duplicates of the data it stores; only overlapped data can contain duplicates.
|
||||
During compaction, the [Compactor](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#compactor) sorts stored data to reduce overlaps and optimize query performance.
|
||||
For data that doesn't have overlaps, the [Querier](/influxdb3/cloud-dedicated/reference/internals/storage-engine/#querier) doesn't need to include the deduplication process and the query plan can further distribute non-overlapping data for parallel processing.
|
||||
|
||||
## DataFusion query plans
|
||||
|
||||
For more information about DataFusion query plans and the DataFusion API used in InfluxDB v3, see the following:
|
||||
For more information about DataFusion query plans and the DataFusion API used in InfluxDB 3, see the following:
|
||||
|
||||
- [Query Planning and Execution Overview](https://docs.rs/datafusion/latest/datafusion/index.html#query-planning-and-execution-overview) in the DataFusion documentation.
|
||||
- [Plan representations](https://docs.rs/datafusion/latest/datafusion/#plan-representations) in the DataFusion documentation.
|
||||
|
|
|
@ -85,7 +85,7 @@ and protected in its own virtual private cloud (VPC).
|
|||
|
||||
Users interact with {{% product-name %}} only through Cloud Dedicated established APIs.
|
||||
For cluster management activities, authorized users interact with the Granite service.
|
||||
For workload clusters, authorized users interact with APIs for InfluxDB v3 Ingesters (writes) and Queriers (reads).
|
||||
For workload clusters, authorized users interact with APIs for InfluxDB 3 Ingesters (writes) and Queriers (reads).
|
||||
These services don't expose AWS S3 or other cloud provider or internal services.
|
||||
{{% product-name %}} uses separate S3 buckets for each customer's cluster to persist writes.
|
||||
The S3 buckets are only accessible by the customer's cluster services.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: InfluxDB v3 storage engine architecture
|
||||
title: InfluxDB 3 storage engine architecture
|
||||
description: >
|
||||
The InfluxDB v3 storage engine is a real-time, columnar database optimized for
|
||||
The InfluxDB 3 storage engine is a real-time, columnar database optimized for
|
||||
time series data that supports infinite tag cardinality, real-time queries,
|
||||
and is optimized to reduce storage cost.
|
||||
weight: 103
|
||||
|
@ -14,7 +14,7 @@ related:
|
|||
- /influxdb3/cloud-dedicated/admin/custom-partitions/
|
||||
---
|
||||
|
||||
The InfluxDB v3 storage engine is a real-time, columnar database optimized for
|
||||
The InfluxDB 3 storage engine is a real-time, columnar database optimized for
|
||||
time series data built in [Rust](https://www.rust-lang.org/) on top of
|
||||
[Apache Arrow](https://arrow.apache.org/) and
|
||||
[DataFusion](https://arrow.apache.org/datafusion/user-guide/introduction.html).
|
||||
|
@ -188,7 +188,7 @@ runs out of memory.
|
|||
|
||||
## Scaling strategies
|
||||
|
||||
The following scaling strategies can be applied to components of the InfluxDB v3
|
||||
The following scaling strategies can be applied to components of the InfluxDB 3
|
||||
storage architecture.
|
||||
|
||||
{{% note %}}
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
title: influxctl release notes
|
||||
list_title: influxctl
|
||||
description: >
|
||||
Release notes for the `influxctl` CLI used to manage InfluxDB v3 clusters.
|
||||
Release notes for the `influxctl` CLI used to manage InfluxDB 3 clusters.
|
||||
menu:
|
||||
influxdb3_cloud_dedicated:
|
||||
identifier: influxctl-release-notes
|
||||
|
@ -330,8 +330,8 @@ This release includes the following notable changes:
|
|||
to allow Cloud Dedicated users without a local UI or browser to continue to
|
||||
use `influxctl`.
|
||||
- Introduce the `influxctl write` and `influxctl query` commands.
|
||||
`influxctl query` queries an InfluxDB v3 instance using SQL.
|
||||
`influxctl write` writes line protocol to a InfluxDB v3 instance.
|
||||
`influxctl query` queries an InfluxDB 3 instance using SQL.
|
||||
`influxctl write` writes line protocol to a InfluxDB 3 instance.
|
||||
|
||||
### Features
|
||||
|
||||
|
@ -494,7 +494,7 @@ configurations now managed in a single configuration file. If using `influxctl`
|
|||
|
||||
### Migrate from influxctl 1.x to 2.0
|
||||
|
||||
`influxctl` 2.0+ supports multiple InfluxDB v3 products.
|
||||
`influxctl` 2.0+ supports multiple InfluxDB 3 products.
|
||||
To simplify connection configuration management, all configurations are now managed
|
||||
in a single file rather than separate files for each connection configuration.
|
||||
|
||||
|
|
|
@ -105,7 +105,7 @@ question as you design your schema.
|
|||
It doesn't index tag values or field values.
|
||||
|
||||
{{% note %}}
|
||||
The InfluxDB v3 storage engine supports infinite tag value and series cardinality.
|
||||
The InfluxDB 3 storage engine supports infinite tag value and series cardinality.
|
||||
Unlike InfluxDB backed by the TSM storage engine, **tag value**
|
||||
cardinality doesn't affect the overall performance of your database.
|
||||
{{% /note %}}
|
||||
|
|
|
@ -144,5 +144,5 @@ data to InfluxDB.
|
|||
The preceding examples describe Telegraf configurations necessary for writing to {{% product-name %}}.
|
||||
The output plugin provides several other options for configuring the Telegraf client:
|
||||
|
||||
- `influx_uint_support`: supported by the InfluxDB v3 storage engine.
|
||||
- `influx_uint_support`: supported by the InfluxDB 3 storage engine.
|
||||
- See [`influxdb_v2` plugin options](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb_v2/README.md) on GitHub.
|
||||
|
|
|
@ -83,8 +83,8 @@ The following example shows how to construct `Point` objects that follow the
|
|||
[example `home` schema](#example-home-schema), and then write the data as line
|
||||
protocol to an {{% product-name %}} database.
|
||||
|
||||
The examples use InfluxDB v3 client libraries. For examples using InfluxDB v2
|
||||
client libraries to write data to InfluxDB v3, see
|
||||
The examples use InfluxDB 3 client libraries. For examples using InfluxDB v2
|
||||
client libraries to write data to InfluxDB 3, see
|
||||
[InfluxDB v2 clients](/influxdb3/cloud-dedicated/reference/client-libraries/v2/).
|
||||
|
||||
{{< tabs-wrapper >}}
|
||||
|
@ -96,7 +96,7 @@ client libraries to write data to InfluxDB v3, see
|
|||
{{% tab-content %}}
|
||||
|
||||
The following steps set up a Go project using the
|
||||
[InfluxDB v3 Go client](https://github.com/InfluxCommunity/influxdb3-go/):
|
||||
[InfluxDB 3 Go client](https://github.com/InfluxCommunity/influxdb3-go/):
|
||||
|
||||
<!-- BEGIN GO PROJECT SETUP -->
|
||||
|
||||
|
@ -129,7 +129,7 @@ The following steps set up a Go project using the
|
|||
<!-- BEGIN NODE.JS PROJECT SETUP -->
|
||||
|
||||
The following steps set up a JavaScript project using the
|
||||
[InfluxDB v3 JavaScript client](https://github.com/InfluxCommunity/influxdb3-js/).
|
||||
[InfluxDB 3 JavaScript client](https://github.com/InfluxCommunity/influxdb3-js/).
|
||||
|
||||
1. Install [Node.js](https://nodejs.org/en/download/).
|
||||
|
||||
|
@ -148,7 +148,7 @@ The following steps set up a JavaScript project using the
|
|||
npm init
|
||||
```
|
||||
|
||||
1. Install the `@influxdata/influxdb3-client` InfluxDB v3 JavaScript client
|
||||
1. Install the `@influxdata/influxdb3-client` InfluxDB 3 JavaScript client
|
||||
library.
|
||||
|
||||
```sh
|
||||
|
@ -162,7 +162,7 @@ The following steps set up a JavaScript project using the
|
|||
<!-- BEGIN PYTHON SETUP PROJECT -->
|
||||
|
||||
The following steps set up a Python project using the
|
||||
[InfluxDB v3 Python client](https://github.com/InfluxCommunity/influxdb3-python/):
|
||||
[InfluxDB 3 Python client](https://github.com/InfluxCommunity/influxdb3-python/):
|
||||
|
||||
1. Install [Python](https://www.python.org/downloads/)
|
||||
|
||||
|
|
|
@ -124,7 +124,7 @@ enabling the InfluxDB v2 output plugin will write data to both v1.x and your {{<
|
|||
|
||||
### Other Telegraf configuration options
|
||||
|
||||
`influx_uint_support`: supported in InfluxDB v3.
|
||||
`influx_uint_support`: supported in InfluxDB 3.
|
||||
|
||||
For more plugin options, see [`influxdb`](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb/README.md) on GitHub.
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: InfluxDB Cloud Serverless documentation
|
||||
description: >
|
||||
InfluxDB Cloud Serverless is a hosted and managed version of InfluxDB v3, the
|
||||
InfluxDB Cloud Serverless is a hosted and managed version of InfluxDB 3, the
|
||||
time series platform designed to handle high write and query loads.
|
||||
Learn how to use and leverage InfluxDB Cloud Serverless in use cases such as
|
||||
monitoring metrics, IoT data, and events.
|
||||
|
@ -14,53 +14,53 @@ weight: 1
|
|||
> [!Note]
|
||||
> This InfluxDB Cloud documentation applies to all [organizations](/influxdb3/cloud-serverless/admin/organizations/) created through
|
||||
> **cloud2.influxdata.com** on or after **January 31, 2023** that are powered by
|
||||
> the InfluxDB v3 storage engine. If your organization was created before this
|
||||
> the InfluxDB 3 storage engine. If your organization was created before this
|
||||
> date or through the Google Cloud Platform (GCP) or Azure marketplaces, see the
|
||||
> [InfluxDB Cloud (TSM) documentation](/influxdb/cloud/).
|
||||
>
|
||||
> To see which storage engine your organization is using,
|
||||
> find the **InfluxDB Cloud powered by** link in your
|
||||
> [InfluxDB Cloud organization homepage](https://cloud2.influxdata.com) version information.
|
||||
> If your organization is using InfluxDB v3, you'll see
|
||||
> If your organization is using InfluxDB 3, you'll see
|
||||
> **InfluxDB Cloud Serverless** followed by the version number.
|
||||
|
||||
> [!Warn]
|
||||
> #### InfluxDB v3 and Flux
|
||||
> #### InfluxDB 3 and Flux
|
||||
>
|
||||
> InfluxDB Cloud Serverless and other InfluxDB v3 products don't support Flux.
|
||||
> InfluxDB Cloud Serverless and other InfluxDB 3 products don't support Flux.
|
||||
> Although Flux might still work with {{% product-name %}}, it isn't
|
||||
> officially supported or optimized for InfluxDB v3.
|
||||
> officially supported or optimized for InfluxDB 3.
|
||||
>
|
||||
> Flux is now in maintenance mode. For more information, see
|
||||
> [The future of Flux](/flux/v0/future-of-flux).
|
||||
|
||||
|
||||
InfluxDB Cloud Serverless is a hosted and managed version of InfluxDB backed
|
||||
by InfluxDB 3.0, the time series platform designed to handle high write and query loads.
|
||||
by InfluxDB 3, the time series platform designed to handle high write and query loads.
|
||||
Learn how to use and leverage InfluxDB Cloud Serverless in use cases such as monitoring
|
||||
metrics, IoT data, and event monitoring.
|
||||
|
||||
<a class="btn" href="/influxdb3/cloud-serverless/get-started/">Get started with InfluxDB Cloud Serverless</a>
|
||||
|
||||
## InfluxDB 3.0
|
||||
## InfluxDB 3
|
||||
|
||||
**InfluxDB 3.0** is InfluxDB's next generation that unlocks series
|
||||
**InfluxDB 3** is InfluxDB's next generation that unlocks series
|
||||
limitations present in the Time Structured Merge Tree (TSM) storage engine and
|
||||
allows infinite series cardinality without any impact on overall database performance.
|
||||
It also brings native **SQL support** and improved InfluxQL performance.
|
||||
|
||||
View the following video for more information about InfluxDB 3.0:
|
||||
View the following video for more information about InfluxDB 3:
|
||||
|
||||
{{< youtube "uwqLWpmlQHM" >}}
|
||||
|
||||
## How do you use InfluxDB 3.0?
|
||||
## How do you use InfluxDB 3?
|
||||
|
||||
All InfluxDB Cloud [accounts](/influxdb3/cloud-serverless/admin/accounts/) and [organizations](/influxdb3/cloud-serverless/admin/organizations/) created through
|
||||
[cloud2.influxdata.com](https://cloud2.influxdata.com) on or after **January 31, 2023**
|
||||
are powered by the InfluxDB 3.0.
|
||||
are powered by the InfluxDB 3.
|
||||
|
||||
To see which storage engine your organization is using,
|
||||
find the **InfluxDB Cloud powered by** link in your
|
||||
[InfluxDB Cloud organization homepage](https://cloud2.influxdata.com) version information.
|
||||
If your organization is using InfluxDB 3.0, you'll see
|
||||
If your organization is using InfluxDB 3, you'll see
|
||||
**InfluxDB Cloud Serverless** followed by the version number.
|
||||
|
|
|
@ -48,7 +48,7 @@ InfluxDB Cloud Serverless has adjustable service quotas applied per account.
|
|||
|
||||
### Storage-level
|
||||
|
||||
The InfluxDB v3 storage engine enforces limits on the storage level that apply
|
||||
The InfluxDB 3 storage engine enforces limits on the storage level that apply
|
||||
to all accounts (Free Plan and Usage-Based Plan).
|
||||
|
||||
- [Terminology](#terminology)
|
||||
|
|
|
@ -17,9 +17,9 @@ alt_links:
|
|||
---
|
||||
|
||||
{{% warn %}}
|
||||
#### Don't use explicit schemas with InfluxDB v3
|
||||
#### Don't use explicit schemas with InfluxDB 3
|
||||
|
||||
Don't use **explicit bucket schemas** with InfluxDB v3.
|
||||
Don't use **explicit bucket schemas** with InfluxDB 3.
|
||||
The sections on this page provide help for managing and troubleshooting `explicit` buckets you may already have.
|
||||
{{% /warn %}}
|
||||
|
||||
|
|
|
@ -12,7 +12,7 @@ influxdb3/cloud-serverless/tags: [get-started]
|
|||
|
||||
InfluxDB {{< current-version >}} is the platform purpose-built to collect, store,
|
||||
process and visualize time series data.
|
||||
The InfluxDB v3.0 storage engine provides a number of benefits including nearly
|
||||
The InfluxDB 3.0 storage engine provides a number of benefits including nearly
|
||||
unlimited series cardinality, improved query performance, and interoperability
|
||||
with widely used data processing tools and platforms.
|
||||
|
||||
|
@ -100,7 +100,7 @@ This tutorial covers many of the recommended tools.
|
|||
| <span style="color:gray">`influxctl` CLI</span> | - | - | - |
|
||||
| [InfluxDB HTTP API](#influxdb-http-api) | **{{< icon "check" >}}** | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| [InfluxDB user interface](#influxdb-user-interface) {{< req text="\* " color="magenta" >}} | **{{< icon "check" >}}** | - | **{{< icon "check" >}}** |
|
||||
| [InfluxDB v3 client libraries](#influxdb-v3-client-libraries){{< req text="\* " color="magenta" >}} | - | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| [InfluxDB 3 client libraries](#influxdb-3-client-libraries){{< req text="\* " color="magenta" >}} | - | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| [InfluxDB v1 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v1/) | - | **{{< icon "check" >}}** | **{{< icon "check" >}}** |
|
||||
| [InfluxDB v2 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v2/) | **{{< icon "check" >}}** | **{{< icon "check" >}}** | - |
|
||||
| Telegraf | - | **{{< icon "check" >}}** | - |
|
||||
|
@ -149,7 +149,7 @@ The `/api/v2/write` v2-compatible endpoint works with existing InfluxDB 2.x tool
|
|||
|
||||
InfluxDB client libraries are community-maintained, language-specific clients that interact with InfluxDB APIs.
|
||||
|
||||
[InfluxDB v3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/) are the recommended client libraries for writing and querying data {{% product-name %}}.
|
||||
[InfluxDB 3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/) are the recommended client libraries for writing and querying data {{% product-name %}}.
|
||||
They use the HTTP API to write data and use Flight gRPC to query data.
|
||||
|
||||
[InfluxDB v2 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v2/) can use `/api/v2` HTTP endpoints to manage resources such as buckets and API tokens, and write data in {{% product-name %}}.
|
||||
|
|
|
@ -46,7 +46,7 @@ The examples in this section of the tutorial query the [**get-started** bucket](
|
|||
|
||||
- [InfluxDB user interface (UI)](?t=InfluxDB+UI#execute-an-sql-query){{< req "\* " >}}
|
||||
- [`influx3` data CLI](?t=influx3+CLI#execute-an-sql-query){{< req "\* " >}}
|
||||
- [InfluxDB v3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/){{< req "\* " >}}
|
||||
- [InfluxDB 3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/){{< req "\* " >}}
|
||||
- [Flight clients](/influxdb3/cloud-serverless/reference/client-libraries/flight/)
|
||||
- [Superset](/influxdb3/cloud-serverless/query-data/sql/execute-queries/superset/)
|
||||
- [Grafana](/influxdb3/cloud-serverless/query-data/sql/execute-queries/grafana/)
|
||||
|
@ -178,7 +178,7 @@ ORDER BY room, _time
|
|||
Get started with one of the following tools for querying data stored in an {{% product-name %}} bucket:
|
||||
|
||||
- **InfluxDB UI**: View your schema, build queries using the query editor, and generate data visualizations.
|
||||
- **InfluxDB v3 client libraries**: Use language-specific (Python, Go, etc.) clients to execute queries in your terminal or custom code.
|
||||
- **InfluxDB 3 client libraries**: Use language-specific (Python, Go, etc.) clients to execute queries in your terminal or custom code.
|
||||
- **influx3 data CLI**: Send queries from your terminal command-line.
|
||||
- **Grafana**: Use the [FlightSQL Data Source plugin](https://grafana.com/grafana/plugins/influxdata-flightsql-datasource/), to query, connect, and visualize data.
|
||||
|
||||
|
@ -255,7 +255,7 @@ See [Query in the Data Explorer](/influxdb3/cloud-serverless/query-data/execute-
|
|||
<!--------------------------- BEGIN influx3 CONTENT --------------------------->
|
||||
{{% influxdb/custom-timestamps %}}
|
||||
|
||||
Query InfluxDB v3 using SQL and the [`influx3` CLI](https://github.com/InfluxCommunity/influxdb3-python-cli).
|
||||
Query InfluxDB 3 using SQL and the [`influx3` CLI](https://github.com/InfluxCommunity/influxdb3-python-cli).
|
||||
|
||||
The following steps include setting up a Python virtual environment already
|
||||
covered in [Get started writing data](/influxdb3/cloud-serverless/get-started/write/?t=Python#write-line-protocol-to-influxdb).
|
||||
|
@ -1009,7 +1009,7 @@ _This tutorial assumes using Maven version 3.9, Java version >= 15, and an `infl
|
|||
* @throws Exception
|
||||
*/
|
||||
public static void main(final String[] args) throws Exception {
|
||||
// Write data to InfluxDB v3.
|
||||
// Write data to InfluxDB 3.
|
||||
Write.writeLineProtocol();
|
||||
// Run the SQL query.
|
||||
Query.querySQL();
|
||||
|
|
|
@ -762,7 +762,7 @@ the failure message.
|
|||
{{% influxdb/custom-timestamps %}}
|
||||
|
||||
To write data to {{% product-name %}} using Go, use the
|
||||
InfluxDB v3 [influxdb3-go client library package](https://github.com/InfluxCommunity/influxdb3-go).
|
||||
InfluxDB 3 [influxdb3-go client library package](https://github.com/InfluxCommunity/influxdb3-go).
|
||||
|
||||
1. Inside of your project directory, create a new module directory and navigate
|
||||
into it.
|
||||
|
@ -1158,7 +1158,7 @@ the failure message.
|
|||
cd influxdb_csharp_client
|
||||
```
|
||||
|
||||
4. Run the following command to install the latest version of the InfluxDB v3 C#
|
||||
4. Run the following command to install the latest version of the InfluxDB 3 C#
|
||||
client library.
|
||||
|
||||
<!--pytest.mark.skip-->
|
||||
|
@ -1386,7 +1386,7 @@ _The tutorial assumes using Maven version 3.9 and Java version >= 15._
|
|||
*/
|
||||
public final class Write {
|
||||
/**
|
||||
* Write data to InfluxDB v3.
|
||||
* Write data to InfluxDB 3.
|
||||
*/
|
||||
private Write() {
|
||||
//not called
|
||||
|
@ -1508,7 +1508,7 @@ _The tutorial assumes using Maven version 3.9 and Java version >= 15._
|
|||
* @throws Exception
|
||||
*/
|
||||
public static void main(final String[] args) throws Exception {
|
||||
// Write data to InfluxDB v3.
|
||||
// Write data to InfluxDB 3.
|
||||
Write.writeLineProtocol();
|
||||
}
|
||||
}
|
||||
|
|
|
@ -183,7 +183,7 @@ To setup and start using client libraries, see the [Get started](/influxdb3/clou
|
|||
|
||||
## Query data
|
||||
|
||||
InfluxDB v3 provides the following protocols for executing a query:
|
||||
InfluxDB 3 provides the following protocols for executing a query:
|
||||
|
||||
- [Flight+gRPC](https://arrow.apache.org/docs/format/Flight.html) request that contains an SQL or InfluxQL query.
|
||||
To learn how to query {{% product-name %}} using Flight and SQL, see the [Get started](/influxdb3/cloud-serverless/get-started/) tutorial.
|
||||
|
@ -196,7 +196,7 @@ InfluxDB v3 provides the following protocols for executing a query:
|
|||
{{% product-name %}} supports many different tools for querying data, including:
|
||||
|
||||
- [`influx3` data CLI](https://github.com/InfluxCommunity/influxdb3-python-cli)
|
||||
- [InfluxDB v3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/)
|
||||
- [InfluxDB 3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/)
|
||||
- [Flight clients](/influxdb3/cloud-serverless/reference/client-libraries/flight/)
|
||||
- [Superset](/influxdb3/cloud-serverless/query-data/sql/execute-queries/superset/)
|
||||
- [Grafana](/influxdb3/cloud-serverless/query-data/sql/execute-queries/grafana/)
|
||||
|
|
|
@ -39,7 +39,7 @@ The following questions will help guide your decision to migrate.
|
|||
**Yes, you should migrate**. Series cardinality is a major limiting factor with
|
||||
the InfluxDB TSM storage engine. The more unique series in your data, the less
|
||||
performant your database.
|
||||
The InfluxDB v3 storage engine supports near limitless series cardinality and is,
|
||||
The InfluxDB 3 storage engine supports near limitless series cardinality and is,
|
||||
without question, the better solution for high series cardinality workloads.
|
||||
|
||||
#### Do you want to use SQL to query your data?
|
||||
|
@ -65,15 +65,15 @@ from the following providers:
|
|||
{{< cloud_regions type=iox-list >}}
|
||||
|
||||
If your deployment requires other cloud providers or regions, you may need to wait
|
||||
until the InfluxDB v3 storage engine is available in a region that meets your requirements.
|
||||
We are currently working to make InfluxDB v3 available on more providers and
|
||||
until the InfluxDB 3 storage engine is available in a region that meets your requirements.
|
||||
We are currently working to make InfluxDB 3 available on more providers and
|
||||
in more regions around the world.
|
||||
|
||||
#### Are you reliant on Flux queries and Flux tasks?
|
||||
|
||||
**You should maybe migrate**. Flux queries are less performant against the
|
||||
InfluxDB v3 storage engine. Flux is optimized to work with the TSM storage engine,
|
||||
but these optimizations do not apply to the on-disk structure of InfluxDB v3.
|
||||
InfluxDB 3 storage engine. Flux is optimized to work with the TSM storage engine,
|
||||
but these optimizations do not apply to the on-disk structure of InfluxDB 3.
|
||||
|
||||
---
|
||||
|
||||
|
@ -81,7 +81,7 @@ but these optimizations do not apply to the on-disk structure of InfluxDB v3.
|
|||
|
||||
Before you migrate from InfluxDB 1.x or 2.x to {{< product-name >}}, there
|
||||
are schema design practices supported by the TSM storage engine that are not
|
||||
supported in the InfluxDB v3 storage engine. Specifically, InfluxDB v3 enforces the following schema restrictions:
|
||||
supported in the InfluxDB 3 storage engine. Specifically, InfluxDB 3 enforces the following schema restrictions:
|
||||
|
||||
- You can't use duplicate names for tags and fields
|
||||
- Measurements can contain up to 200 columns where each column represents time,
|
||||
|
|
|
@ -39,7 +39,7 @@ adjustable quotas, migrate your data in batches.
|
|||
|
||||
Before you migrate from InfluxDB 1.x to {{< product-name >}}, there
|
||||
are schema design practices supported by the TSM storage engine that are not
|
||||
supported in the InfluxDB v3 storage engine. Specifically, InfluxDB v3 enforces the following schema restrictions:
|
||||
supported in the InfluxDB 3 storage engine. Specifically, InfluxDB 3 enforces the following schema restrictions:
|
||||
|
||||
- You can't use duplicate names for tags and fields
|
||||
- Measurements can contain up to 200 columns where each column represents time,
|
||||
|
|
|
@ -3,7 +3,7 @@ title: Migrate data from TSM to InfluxDB Cloud Serverless
|
|||
description: >
|
||||
To migrate data from a TSM-powered InfluxDB Cloud organization to an InfluxDB
|
||||
Cloud Serverless organization powered by the v3 storage engine, query the data in
|
||||
time-based batches and write the queried data to an InfluxDB v3 bucket in your
|
||||
time-based batches and write the queried data to an InfluxDB 3 bucket in your
|
||||
InfluxDB Cloud Serverless organization.
|
||||
menu:
|
||||
influxdb_cloud_serverless:
|
||||
|
@ -28,7 +28,7 @@ adjustable quotas, migrate your data in batches.
|
|||
|
||||
The following guide provides instructions for setting up an InfluxDB task
|
||||
that queries data from an InfluxDB Cloud TSM-powered bucket in time-based batches
|
||||
and writes each batch to an InfluxDB Cloud Serverless (InfluxDB v3) bucket in
|
||||
and writes each batch to an InfluxDB Cloud Serverless (InfluxDB 3) bucket in
|
||||
another organization.
|
||||
|
||||
> [!Important]
|
||||
|
@ -48,7 +48,7 @@ another organization.
|
|||
|
||||
Before you migrate from InfluxDB Cloud (TSM) to {{< product-name >}}, there
|
||||
are schema design practices supported by the TSM storage engine that are not
|
||||
supported in the InfluxDB v3 storage engine. Specifically, InfluxDB v3 enforces the following schema restrictions:
|
||||
supported in the InfluxDB 3 storage engine. Specifically, InfluxDB 3 enforces the following schema restrictions:
|
||||
|
||||
- You can't use duplicate names for tags and fields
|
||||
- Measurements can contain up to 200 columns where each column represents time,
|
||||
|
|
|
@ -59,13 +59,13 @@ able to evaluate the Cloud Dedicated administrative features directly.
|
|||
|
||||
### Terminology differences
|
||||
|
||||
InfluxDB Cloud Serverless was an upgrade that introduced the InfluxDB 3.0 storage
|
||||
InfluxDB Cloud Serverless was an upgrade that introduced the InfluxDB 3 storage
|
||||
engine to InfluxData’s original InfluxDB Cloud (TSM) multi-tenant solution.
|
||||
InfluxDB Cloud utilizes the Time-Structured Merge Tree (TSM) storage engine in
|
||||
which databases were referred to as _buckets_.
|
||||
Cloud Serverless still uses this term.
|
||||
|
||||
InfluxDB Cloud Dedicated has only ever used the InfluxDB 3.0 storage engine.
|
||||
InfluxDB Cloud Dedicated has only ever used the InfluxDB 3 storage engine.
|
||||
Resource names in Cloud Dedicated are more traditionally aligned with SQL database engines.
|
||||
Databases are named "databases" and "measurements" are structured as tables.
|
||||
"Tables" or "measurements" can be used interchangeably.
|
||||
|
@ -111,11 +111,11 @@ platform for InfluxDB Cloud Dedicated.
|
|||
For writing data, InfluxDB Cloud Dedicated and InfluxDB Cloud Serverless both
|
||||
support the v1 API and the v2 write API.
|
||||
|
||||
In addition, [InfluxDB v3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/)
|
||||
In addition, [InfluxDB 3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/)
|
||||
are available that work the same for both InfluxDB Cloud Serverless and InfluxDB
|
||||
Cloud Dedicated and help avoid any API differences between the two platforms.
|
||||
For more detailed information about choosing a client library, see the
|
||||
_[Choosing a Client Library When Developing with InfluxDB 3.0](https://www.influxdata.com/blog/choosing-client-library-when-developing-with-influxdb-3-0/)_
|
||||
_[Choosing a Client Library When Developing with InfluxDB 3](https://www.influxdata.com/blog/choosing-client-library-when-developing-with-influxdb-3-0/)_
|
||||
blog post.
|
||||
|
||||
### Tasks and alerts differences
|
||||
|
@ -204,7 +204,7 @@ mentioned in _[Tasks and alerts differences](#tasks-and-alerts-differences)_).
|
|||
|
||||
### Use SQL or InfluxQL as your Query Language
|
||||
|
||||
SQL and InfluxQL are optimized for InfluxDB v3 and both are excellent
|
||||
SQL and InfluxQL are optimized for InfluxDB 3 and both are excellent
|
||||
options in Cloud Dedicated and Cloud Serverless.
|
||||
Avoid Flux since it can’t be used with InfluxDB Cloud Dedicated.
|
||||
|
||||
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue