From 864d6f57e455de5e1c74666fbfdaa46977b042b3 Mon Sep 17 00:00:00 2001 From: Scott Anderson Date: Sun, 12 Jan 2025 20:23:18 -0700 Subject: [PATCH] update use of 3.0 and v3 to just 3 --- .../enterprise_influxdb/v1/tools/grafana.md | 2 +- content/flux/v0/future-of-flux.md | 14 ++++---- .../cloud/account-management/switch-org.md | 4 +-- .../cloud/admin/organizations/_index.md | 4 +-- content/influxdb/cloud/migrate-regions.md | 4 +-- content/influxdb/cloud/upgrade/v2-to-cloud.md | 4 +-- .../migrate-data/migrate-cloud-to-cloud.md | 4 +-- .../v1/about_the_project/release-notes.md | 4 +-- content/influxdb/v1/tools/api.md | 16 +++++----- .../influxdb/v1/tools/api_client_libraries.md | 2 +- content/influxdb/v1/tools/grafana.md | 2 +- content/influxdb/v2/reference/glossary.md | 6 ++-- content/influxdb/v2/tools/grafana.md | 2 +- content/influxdb3/cloud-dedicated/_index.md | 6 ++-- .../custom-partitions/view-partitions.md | 2 +- .../cloud-dedicated/admin/databases/create.md | 4 +-- .../admin/monitor-your-cluster.md | 2 +- .../admin/query-system-data.md | 6 ++-- .../cloud-dedicated/admin/tables/create.md | 2 +- .../cloud-dedicated/get-started/_index.md | 6 ++-- .../cloud-dedicated/get-started/query.md | 8 ++--- .../cloud-dedicated/get-started/write.md | 8 ++--- .../guides/api-compatibility/v1/_index.md | 4 +-- .../guides/api-compatibility/v2/_index.md | 2 +- .../guides/migrate-data/_index.md | 6 ++-- .../migrate-1x-to-cloud-dedicated.md | 2 +- .../migrate-tsm-to-cloud-dedicated.md | 6 ++-- .../guides/prototype-evaluation.md | 10 +++--- content/influxdb3/cloud-dedicated/pages.md | 2 +- .../downsample/downsample-client-libraries.md | 4 +-- .../downsample/downsample-quix.md | 6 ++-- .../process-data/send-alerts.md | 4 +-- .../process-data/tools/pandas.md | 2 +- .../process-data/tools/pyarrow.md | 2 +- .../process-data/visualize/chronograf.md | 2 +- .../process-data/visualize/grafana.md | 2 +- .../client-libraries/_index.md | 8 ++--- .../execute-queries/influxdb-v1-api.md | 2 +- .../execute-queries/visualization-tools.md | 2 +- .../influxql/parameterized-queries.md | 10 +++--- .../query-data/sql/parameterized-queries.md | 10 +++--- .../analyze-query-plan.md | 4 +-- .../flight-responses.md | 4 +-- .../optimize-queries.md | 4 +-- .../system-information.md | 2 +- .../reference/cli/influxctl/_index.md | 16 +++++----- .../reference/cli/influxctl/query.md | 32 +++++++++---------- .../reference/cli/influxctl/write.md | 18 +++++------ .../client-libraries/flight/_index.md | 6 ++-- .../client-libraries/flight/csharp-flight.md | 6 ++-- .../client-libraries/flight/go-flight.md | 6 ++-- .../client-libraries/flight/java-flightsql.md | 8 ++--- .../client-libraries/flight/python-flight.md | 6 ++-- .../flight/python-flightsql-dbapi.md | 6 ++-- .../reference/client-libraries/v1/_index.md | 2 +- .../reference/client-libraries/v2/_index.md | 6 ++-- .../reference/client-libraries/v2/arduino.md | 6 ++-- .../reference/client-libraries/v2/csharp.md | 6 ++-- .../reference/client-libraries/v2/dart.md | 6 ++-- .../reference/client-libraries/v2/go.md | 6 ++-- .../reference/client-libraries/v2/java.md | 6 ++-- .../client-libraries/v2/javascript/_index.md | 6 ++-- .../client-libraries/v2/javascript/browser.md | 6 ++-- .../v2/javascript/nodejs/_index.md | 6 ++-- .../v2/javascript/nodejs/install.md | 6 ++-- .../v2/javascript/nodejs/write.md | 6 ++-- .../reference/client-libraries/v2/kotlin.md | 6 ++-- .../reference/client-libraries/v2/php.md | 6 ++-- .../reference/client-libraries/v2/python.md | 6 ++-- .../reference/client-libraries/v2/r.md | 6 ++-- .../reference/client-libraries/v2/ruby.md | 6 ++-- .../reference/client-libraries/v2/scala.md | 6 ++-- .../reference/client-libraries/v2/swift.md | 6 ++-- .../reference/client-libraries/v3/_index.md | 12 +++---- .../reference/client-libraries/v3/csharp.md | 8 ++--- .../reference/client-libraries/v3/go.md | 10 +++--- .../reference/client-libraries/v3/java.md | 12 +++---- .../client-libraries/v3/javascript.md | 8 ++--- .../reference/client-libraries/v3/python.md | 10 +++--- .../cloud-dedicated/reference/glossary.md | 6 ++-- .../reference/influxql/feature-support.md | 2 +- .../reference/internals/query-plan.md | 10 +++--- .../reference/internals/security.md | 2 +- .../reference/internals/storage-engine.md | 8 ++--- .../reference/release-notes/influxctl.md | 8 ++--- .../best-practices/schema-design.md | 2 +- .../write-data/csv/telegraf.md | 2 +- .../line-protocol/client-libraries.md | 12 +++---- .../use-telegraf/configure/_index.md | 2 +- content/influxdb3/cloud-serverless/_index.md | 26 +++++++-------- .../cloud-serverless/admin/billing/limits.md | 2 +- .../buckets/manage-explicit-bucket-schemas.md | 4 +-- .../cloud-serverless/get-started/_index.md | 6 ++-- .../cloud-serverless/get-started/query.md | 8 ++--- .../cloud-serverless/get-started/write.md | 8 ++--- .../guides/api-compatibility/v2/_index.md | 4 +-- .../guides/migrate-data/_index.md | 12 +++---- .../migrate-data/migrate-1x-to-serverless.md | 2 +- .../migrate-data/migrate-tsm-to-serverless.md | 6 ++-- .../guides/prototype-evaluation.md | 10 +++--- content/influxdb3/cloud-serverless/pages.md | 2 +- .../downsample/client-libraries.md | 4 +-- .../process-data/downsample/quix.md | 6 ++-- .../process-data/send-alerts.md | 4 +-- .../process-data/tools/pandas.md | 2 +- .../process-data/tools/pyarrow.md | 2 +- .../process-data/visualize/chronograf.md | 2 +- .../process-data/visualize/grafana.md | 2 +- .../query-data/execute-queries/_index.md | 6 ++-- .../client-libraries/_index.md | 8 ++--- .../query-data/execute-queries/v1-http.md | 2 +- .../execute-queries/visualization-tools.md | 2 +- .../influxql/parameterized-queries.md | 10 +++--- .../query-data/sql/parameterized-queries.md | 10 +++--- .../analyze-query-plan.md | 4 +-- .../flight-responses.md | 4 +-- .../optimize-queries.md | 4 +-- .../reference/cli/influx/apply/_index.md | 2 +- .../reference/cli/influx/dashboards/_index.md | 2 +- .../reference/cli/influx/export/_index.md | 2 +- .../client-libraries/flight/_index.md | 6 ++-- .../client-libraries/flight/csharp-flight.md | 6 ++-- .../client-libraries/flight/go-flight.md | 6 ++-- .../client-libraries/flight/java-flightsql.md | 8 ++--- .../client-libraries/flight/python-flight.md | 6 ++-- .../flight/python-flightsql-dbapi.md | 6 ++-- .../reference/client-libraries/v1/_index.md | 2 +- .../reference/client-libraries/v2/_index.md | 6 ++-- .../reference/client-libraries/v2/arduino.md | 6 ++-- .../reference/client-libraries/v2/csharp.md | 6 ++-- .../reference/client-libraries/v2/dart.md | 6 ++-- .../reference/client-libraries/v2/go.md | 6 ++-- .../reference/client-libraries/v2/java.md | 6 ++-- .../client-libraries/v2/javascript/_index.md | 6 ++-- .../client-libraries/v2/javascript/browser.md | 6 ++-- .../v2/javascript/nodejs/_index.md | 6 ++-- .../v2/javascript/nodejs/install.md | 6 ++-- .../v2/javascript/nodejs/write.md | 6 ++-- .../reference/client-libraries/v2/kotlin.md | 6 ++-- .../reference/client-libraries/v2/php.md | 6 ++-- .../reference/client-libraries/v2/python.md | 8 ++--- .../reference/client-libraries/v2/r.md | 6 ++-- .../reference/client-libraries/v2/ruby.md | 6 ++-- .../reference/client-libraries/v2/scala.md | 6 ++-- .../reference/client-libraries/v2/swift.md | 6 ++-- .../reference/client-libraries/v3/_index.md | 12 +++---- .../reference/client-libraries/v3/csharp.md | 8 ++--- .../reference/client-libraries/v3/go.md | 10 +++--- .../reference/client-libraries/v3/java.md | 12 +++---- .../client-libraries/v3/javascript.md | 8 ++--- .../reference/client-libraries/v3/python.md | 12 +++---- .../cloud-serverless/reference/glossary.md | 10 +++--- .../reference/influxql/feature-support.md | 2 +- .../reference/internals/query-plan.md | 10 +++--- .../cloud-serverless/reference/regions.md | 4 +-- content/influxdb3/cloud-serverless/sign-up.md | 4 +-- .../write-data/api/v1-http.md | 4 +-- .../best-practices/schema-design.md | 2 +- .../write-data/csv/telegraf.md | 2 +- .../line-protocol/client-libraries.md | 12 +++---- content/influxdb3/clustered/_index.md | 10 +++--- .../custom-partitions/view-partitions.md | 2 +- .../clustered/admin/databases/create.md | 2 +- content/influxdb3/clustered/admin/env-vars.md | 4 +-- .../clustered/admin/query-system-data.md | 6 ++-- .../clustered/admin/tables/create.md | 2 +- .../influxdb3/clustered/get-started/_index.md | 6 ++-- .../influxdb3/clustered/get-started/query.md | 8 ++--- .../influxdb3/clustered/get-started/write.md | 8 ++--- .../guides/api-compatibility/v1/_index.md | 4 +-- .../guides/api-compatibility/v2/_index.md | 2 +- .../clustered/guides/migrate-data/_index.md | 8 ++--- .../migrate-data/migrate-1x-to-clustered.md | 2 +- .../migrate-data/migrate-tsm-to-clustered.md | 6 ++-- content/influxdb3/clustered/install/_index.md | 4 +-- .../install/optimize-cluster/write-methods.md | 2 +- content/influxdb3/clustered/pages.md | 2 +- .../downsample/downsample-client-libraries.md | 4 +-- .../clustered/process-data/downsample/quix.md | 6 ++-- .../clustered/process-data/send-alerts.md | 4 +-- .../clustered/process-data/tools/pandas.md | 2 +- .../clustered/process-data/tools/pyarrow.md | 2 +- .../process-data/visualize/chronograf.md | 2 +- .../process-data/visualize/grafana.md | 2 +- .../client-libraries/_index.md | 8 ++--- .../execute-queries/influxdb-v1-api.md | 2 +- .../execute-queries/visualization-tools.md | 2 +- .../influxql/parameterized-queries.md | 10 +++--- .../query-data/sql/parameterized-queries.md | 10 +++--- .../analyze-query-plan.md | 4 +-- .../flight-responses.md | 4 +-- .../optimize-queries.md | 4 +-- .../report-query-performance-issues.md | 2 +- .../reference/cli/influxctl/_index.md | 18 +++++------ .../reference/cli/influxctl/query.md | 32 +++++++++---------- .../reference/cli/influxctl/write.md | 20 ++++++------ .../client-libraries/flight/_index.md | 6 ++-- .../client-libraries/flight/csharp-flight.md | 6 ++-- .../client-libraries/flight/go-flight.md | 6 ++-- .../client-libraries/flight/java-flightsql.md | 8 ++--- .../client-libraries/flight/python-flight.md | 6 ++-- .../flight/python-flightsql-dbapi.md | 6 ++-- .../reference/client-libraries/v1/_index.md | 2 +- .../reference/client-libraries/v2/_index.md | 6 ++-- .../reference/client-libraries/v2/arduino.md | 6 ++-- .../reference/client-libraries/v2/csharp.md | 6 ++-- .../reference/client-libraries/v2/dart.md | 6 ++-- .../reference/client-libraries/v2/go.md | 6 ++-- .../reference/client-libraries/v2/java.md | 6 ++-- .../client-libraries/v2/javascript/_index.md | 6 ++-- .../client-libraries/v2/javascript/browser.md | 6 ++-- .../v2/javascript/nodejs/_index.md | 6 ++-- .../v2/javascript/nodejs/install.md | 6 ++-- .../v2/javascript/nodejs/write.md | 6 ++-- .../reference/client-libraries/v2/kotlin.md | 6 ++-- .../reference/client-libraries/v2/php.md | 6 ++-- .../reference/client-libraries/v2/python.md | 6 ++-- .../reference/client-libraries/v2/r.md | 6 ++-- .../reference/client-libraries/v2/ruby.md | 6 ++-- .../reference/client-libraries/v2/scala.md | 6 ++-- .../reference/client-libraries/v2/swift.md | 6 ++-- .../reference/client-libraries/v3/_index.md | 12 +++---- .../reference/client-libraries/v3/csharp.md | 8 ++--- .../reference/client-libraries/v3/go.md | 10 +++--- .../reference/client-libraries/v3/java.md | 12 +++---- .../client-libraries/v3/javascript.md | 8 ++--- .../reference/client-libraries/v3/python.md | 10 +++--- .../influxdb3/clustered/reference/glossary.md | 8 ++--- .../reference/influxql/feature-support.md | 2 +- .../reference/internals/query-plan.md | 10 +++--- .../reference/internals/storage-engine.md | 6 ++-- .../reference/release-notes/clustered.md | 4 +-- .../reference/release-notes/influxctl.md | 8 ++--- .../best-practices/schema-design.md | 2 +- .../clustered/write-data/csv/telegraf.md | 2 +- .../line-protocol/client-libraries.md | 12 +++---- .../use-telegraf/configure/_index.md | 2 +- content/influxdb3/core/_index.md | 2 +- .../reference/influxql/feature-support.md | 2 +- .../reference/influxql/feature-support.md | 2 +- .../shared/influxql-v3-reference/_index.md | 2 +- .../influxql-v3-reference/feature-support.md | 6 ++-- .../influxql-v3-reference/functions/_index.md | 2 +- .../functions/aggregates.md | 2 +- .../functions/selectors.md | 2 +- .../functions/transformations.md | 2 +- .../influxql-v3-reference/limit-and-slimit.md | 2 +- .../offset-and-soffset.md | 2 +- .../_index.md | 6 ++-- .../view-partitions.md | 4 +-- 250 files changed, 743 insertions(+), 743 deletions(-) diff --git a/content/enterprise_influxdb/v1/tools/grafana.md b/content/enterprise_influxdb/v1/tools/grafana.md index 85e8042d5..271279626 100644 --- a/content/enterprise_influxdb/v1/tools/grafana.md +++ b/content/enterprise_influxdb/v1/tools/grafana.md @@ -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 >}} diff --git a/content/flux/v0/future-of-flux.md b/content/flux/v0/future-of-flux.md index f283b84b2..3417d9f0a 100644 --- a/content/flux/v0/future-of-flux.md +++ b/content/flux/v0/future-of-flux.md @@ -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 diff --git a/content/influxdb/cloud/account-management/switch-org.md b/content/influxdb/cloud/account-management/switch-org.md index bcaa5ef28..b91e35403 100644 --- a/content/influxdb/cloud/account-management/switch-org.md +++ b/content/influxdb/cloud/account-management/switch-org.md @@ -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) diff --git a/content/influxdb/cloud/admin/organizations/_index.md b/content/influxdb/cloud/admin/organizations/_index.md index 11c79ab51..941173281 100644 --- a/content/influxdb/cloud/admin/organizations/_index.md +++ b/content/influxdb/cloud/admin/organizations/_index.md @@ -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) diff --git a/content/influxdb/cloud/migrate-regions.md b/content/influxdb/cloud/migrate-regions.md index 86211b210..628fa8ace 100644 --- a/content/influxdb/cloud/migrate-regions.md +++ b/content/influxdb/cloud/migrate-regions.md @@ -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/) diff --git a/content/influxdb/cloud/upgrade/v2-to-cloud.md b/content/influxdb/cloud/upgrade/v2-to-cloud.md index 9b92083e2..49dd639b0 100644 --- a/content/influxdb/cloud/upgrade/v2-to-cloud.md +++ b/content/influxdb/cloud/upgrade/v2-to-cloud.md @@ -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) diff --git a/content/influxdb/cloud/write-data/migrate-data/migrate-cloud-to-cloud.md b/content/influxdb/cloud/write-data/migrate-data/migrate-cloud-to-cloud.md index 7eefb0466..02a06cab6 100644 --- a/content/influxdb/cloud/write-data/migrate-data/migrate-cloud-to-cloud.md +++ b/content/influxdb/cloud/write-data/migrate-data/migrate-cloud-to-cloud.md @@ -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) diff --git a/content/influxdb/v1/about_the_project/release-notes.md b/content/influxdb/v1/about_the_project/release-notes.md index 5c824f76d..aa82116c8 100644 --- a/content/influxdb/v1/about_the_project/release-notes.md +++ b/content/influxdb/v1/about_the_project/release-notes.md @@ -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 diff --git a/content/influxdb/v1/tools/api.md b/content/influxdb/v1/tools/api.md index 9843c3e4d..237bfb732 100644 --- a/content/influxdb/v1/tools/api.md +++ b/content/influxdb/v1/tools/api.md @@ -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 diff --git a/content/influxdb/v1/tools/api_client_libraries.md b/content/influxdb/v1/tools/api_client_libraries.md index aea013e41..681966893 100644 --- a/content/influxdb/v1/tools/api_client_libraries.md +++ b/content/influxdb/v1/tools/api_client_libraries.md @@ -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/). diff --git a/content/influxdb/v1/tools/grafana.md b/content/influxdb/v1/tools/grafana.md index 27d1bfeff..b19bb6e18 100644 --- a/content/influxdb/v1/tools/grafana.md +++ b/content/influxdb/v1/tools/grafana.md @@ -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 >}} diff --git a/content/influxdb/v2/reference/glossary.md b/content/influxdb/v2/reference/glossary.md index 185ec057c..bee87131d 100644 --- a/content/influxdb/v2/reference/glossary.md +++ b/content/influxdb/v2/reference/glossary.md @@ -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) diff --git a/content/influxdb/v2/tools/grafana.md b/content/influxdb/v2/tools/grafana.md index 35693e6f8..9d3fcf76e 100644 --- a/content/influxdb/v2/tools/grafana.md +++ b/content/influxdb/v2/tools/grafana.md @@ -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 >}} diff --git a/content/influxdb3/cloud-dedicated/_index.md b/content/influxdb3/cloud-dedicated/_index.md index 42ea91b87..c2708a8c2 100644 --- a/content/influxdb3/cloud-dedicated/_index.md +++ b/content/influxdb3/cloud-dedicated/_index.md @@ -21,13 +21,13 @@ time series use case. Request an InfluxDB Cloud Dedicated cluster Get started with InfluxDB Cloud Dedicated -## 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" >}} diff --git a/content/influxdb3/cloud-dedicated/admin/custom-partitions/view-partitions.md b/content/influxdb3/cloud-dedicated/admin/custom-partitions/view-partitions.md index 7722e92f4..82865a5b4 100644 --- a/content/influxdb3/cloud-dedicated/admin/custom-partitions/view-partitions.md +++ b/content/influxdb3/cloud-dedicated/admin/custom-partitions/view-partitions.md @@ -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: diff --git a/content/influxdb3/cloud-dedicated/admin/databases/create.md b/content/influxdb3/cloud-dedicated/admin/databases/create.md index 4cb8b7765..c5ae29e02 100644 --- a/content/influxdb3/cloud-dedicated/admin/databases/create.md +++ b/content/influxdb3/cloud-dedicated/admin/databases/create.md @@ -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. diff --git a/content/influxdb3/cloud-dedicated/admin/monitor-your-cluster.md b/content/influxdb3/cloud-dedicated/admin/monitor-your-cluster.md index 71f09091d..b8353b526 100644 --- a/content/influxdb3/cloud-dedicated/admin/monitor-your-cluster.md +++ b/content/influxdb3/cloud-dedicated/admin/monitor-your-cluster.md @@ -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. diff --git a/content/influxdb3/cloud-dedicated/admin/query-system-data.md b/content/influxdb3/cloud-dedicated/admin/query-system-data.md index 340d81012..57c7eafd8 100644 --- a/content/influxdb3/cloud-dedicated/admin/query-system-data.md +++ b/content/influxdb3/cloud-dedicated/admin/query-system-data.md @@ -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). diff --git a/content/influxdb3/cloud-dedicated/admin/tables/create.md b/content/influxdb3/cloud-dedicated/admin/tables/create.md index db27bcc97..e755521b4 100644 --- a/content/influxdb3/cloud-dedicated/admin/tables/create.md +++ b/content/influxdb3/cloud-dedicated/admin/tables/create.md @@ -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. diff --git a/content/influxdb3/cloud-dedicated/get-started/_index.md b/content/influxdb3/cloud-dedicated/get-started/_index.md index fca345bfe..3075bd84f 100644 --- a/content/influxdb3/cloud-dedicated/get-started/_index.md +++ b/content/influxdb3/cloud-dedicated/get-started/_index.md @@ -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" >}}** | | InfluxDB user interface | - | - | - | -| [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. diff --git a/content/influxdb3/cloud-dedicated/get-started/query.md b/content/influxdb3/cloud-dedicated/get-started/query.md index a6bb5b46e..814cdd107 100644 --- a/content/influxdb3/cloud-dedicated/get-started/query.md +++ b/content/influxdb3/cloud-dedicated/get-started/query.md @@ -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. {{% 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(); diff --git a/content/influxdb3/cloud-dedicated/get-started/write.md b/content/influxdb3/cloud-dedicated/get-started/write.md index 14004896f..07f9e280e 100644 --- a/content/influxdb3/cloud-dedicated/get-started/write.md +++ b/content/influxdb3/cloud-dedicated/get-started/write.md @@ -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. @@ -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(); } } diff --git a/content/influxdb3/cloud-dedicated/guides/api-compatibility/v1/_index.md b/content/influxdb3/cloud-dedicated/guides/api-compatibility/v1/_index.md index e294d327f..ea6279fae 100644 --- a/content/influxdb3/cloud-dedicated/guides/api-compatibility/v1/_index.md +++ b/content/influxdb3/cloud-dedicated/guides/api-compatibility/v1/_index.md @@ -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/) diff --git a/content/influxdb3/cloud-dedicated/guides/api-compatibility/v2/_index.md b/content/influxdb3/cloud-dedicated/guides/api-compatibility/v2/_index.md index 6031a67b8..d41b067ad 100644 --- a/content/influxdb3/cloud-dedicated/guides/api-compatibility/v2/_index.md +++ b/content/influxdb3/cloud-dedicated/guides/api-compatibility/v2/_index.md @@ -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/) diff --git a/content/influxdb3/cloud-dedicated/guides/migrate-data/_index.md b/content/influxdb3/cloud-dedicated/guides/migrate-data/_index.md index 5c5fda92f..4528cfec7 100644 --- a/content/influxdb3/cloud-dedicated/guides/migrate-data/_index.md +++ b/content/influxdb3/cloud-dedicated/guides/migrate-data/_index.md @@ -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 diff --git a/content/influxdb3/cloud-dedicated/guides/migrate-data/migrate-1x-to-cloud-dedicated.md b/content/influxdb3/cloud-dedicated/guides/migrate-data/migrate-1x-to-cloud-dedicated.md index 4f9bcf35b..47c4432f9 100644 --- a/content/influxdb3/cloud-dedicated/guides/migrate-data/migrate-1x-to-cloud-dedicated.md +++ b/content/influxdb3/cloud-dedicated/guides/migrate-data/migrate-1x-to-cloud-dedicated.md @@ -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 diff --git a/content/influxdb3/cloud-dedicated/guides/migrate-data/migrate-tsm-to-cloud-dedicated.md b/content/influxdb3/cloud-dedicated/guides/migrate-data/migrate-tsm-to-cloud-dedicated.md index dcca31fc6..638651d37 100644 --- a/content/influxdb3/cloud-dedicated/guides/migrate-data/migrate-tsm-to-cloud-dedicated.md +++ b/content/influxdb3/cloud-dedicated/guides/migrate-data/migrate-tsm-to-cloud-dedicated.md @@ -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 diff --git a/content/influxdb3/cloud-dedicated/guides/prototype-evaluation.md b/content/influxdb3/cloud-dedicated/guides/prototype-evaluation.md index 7e6b43e50..2d87e1354 100644 --- a/content/influxdb3/cloud-dedicated/guides/prototype-evaluation.md +++ b/content/influxdb3/cloud-dedicated/guides/prototype-evaluation.md @@ -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. diff --git a/content/influxdb3/cloud-dedicated/pages.md b/content/influxdb3/cloud-dedicated/pages.md index 3581f182a..feed7e459 100644 --- a/content/influxdb3/cloud-dedicated/pages.md +++ b/content/influxdb3/cloud-dedicated/pages.md @@ -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. diff --git a/content/influxdb3/cloud-dedicated/process-data/downsample/downsample-client-libraries.md b/content/influxdb3/cloud-dedicated/process-data/downsample/downsample-client-libraries.md index b7fb10d67..8f6670238 100644 --- a/content/influxdb3/cloud-dedicated/process-data/downsample/downsample-client-libraries.md +++ b/content/influxdb3/cloud-dedicated/process-data/downsample/downsample-client-libraries.md @@ -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). diff --git a/content/influxdb3/cloud-dedicated/process-data/downsample/downsample-quix.md b/content/influxdb3/cloud-dedicated/process-data/downsample/downsample-quix.md index 92ee33263..a9dcfae45 100644 --- a/content/influxdb3/cloud-dedicated/process-data/downsample/downsample-quix.md +++ b/content/influxdb3/cloud-dedicated/process-data/downsample/downsample-quix.md @@ -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', diff --git a/content/influxdb3/cloud-dedicated/process-data/send-alerts.md b/content/influxdb3/cloud-dedicated/process-data/send-alerts.md index 6b4f5fd36..d4c8183d1 100644 --- a/content/influxdb3/cloud-dedicated/process-data/send-alerts.md +++ b/content/influxdb3/cloud-dedicated/process-data/send-alerts.md @@ -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 diff --git a/content/influxdb3/cloud-dedicated/process-data/tools/pandas.md b/content/influxdb3/cloud-dedicated/process-data/tools/pandas.md index 99d5b9cf3..aa0e6b9b1 100644 --- a/content/influxdb3/cloud-dedicated/process-data/tools/pandas.md +++ b/content/influxdb3/cloud-dedicated/process-data/tools/pandas.md @@ -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. diff --git a/content/influxdb3/cloud-dedicated/process-data/tools/pyarrow.md b/content/influxdb3/cloud-dedicated/process-data/tools/pyarrow.md index 4bf0a5096..68d2efb3a 100644 --- a/content/influxdb3/cloud-dedicated/process-data/tools/pyarrow.md +++ b/content/influxdb3/cloud-dedicated/process-data/tools/pyarrow.md @@ -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. diff --git a/content/influxdb3/cloud-dedicated/process-data/visualize/chronograf.md b/content/influxdb3/cloud-dedicated/process-data/visualize/chronograf.md index 4c682f6c3..ea37355f7 100644 --- a/content/influxdb3/cloud-dedicated/process-data/visualize/chronograf.md +++ b/content/influxdb3/cloud-dedicated/process-data/visualize/chronograf.md @@ -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/). diff --git a/content/influxdb3/cloud-dedicated/process-data/visualize/grafana.md b/content/influxdb3/cloud-dedicated/process-data/visualize/grafana.md index 1345c9be9..9ba7d31f9 100644 --- a/content/influxdb3/cloud-dedicated/process-data/visualize/grafana.md +++ b/content/influxdb3/cloud-dedicated/process-data/visualize/grafana.md @@ -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 %}} diff --git a/content/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/_index.md b/content/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/_index.md index f21a09543..f5876ef66 100644 --- a/content/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/_index.md +++ b/content/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/_index.md @@ -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" >}} diff --git a/content/influxdb3/cloud-dedicated/query-data/execute-queries/influxdb-v1-api.md b/content/influxdb3/cloud-dedicated/query-data/execute-queries/influxdb-v1-api.md index 76586433e..c27dd332d 100644 --- a/content/influxdb3/cloud-dedicated/query-data/execute-queries/influxdb-v1-api.md +++ b/content/influxdb3/cloud-dedicated/query-data/execute-queries/influxdb-v1-api.md @@ -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/). diff --git a/content/influxdb3/cloud-dedicated/query-data/execute-queries/visualization-tools.md b/content/influxdb3/cloud-dedicated/query-data/execute-queries/visualization-tools.md index ce96ea976..1e72b4c2a 100644 --- a/content/influxdb3/cloud-dedicated/query-data/execute-queries/visualization-tools.md +++ b/content/influxdb3/cloud-dedicated/query-data/execute-queries/visualization-tools.md @@ -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/). diff --git a/content/influxdb3/cloud-dedicated/query-data/influxql/parameterized-queries.md b/content/influxdb3/cloud-dedicated/query-data/influxql/parameterized-queries.md index daab2f1ca..cea109f13 100644 --- a/content/influxdb3/cloud-dedicated/query-data/influxql/parameterized-queries.md +++ b/content/influxdb3/cloud-dedicated/query-data/influxql/parameterized-queries.md @@ -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 diff --git a/content/influxdb3/cloud-dedicated/query-data/sql/parameterized-queries.md b/content/influxdb3/cloud-dedicated/query-data/sql/parameterized-queries.md index 8a0e5a163..a3cfdfbc0 100644 --- a/content/influxdb3/cloud-dedicated/query-data/sql/parameterized-queries.md +++ b/content/influxdb3/cloud-dedicated/query-data/sql/parameterized-queries.md @@ -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 diff --git a/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/analyze-query-plan.md b/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/analyze-query-plan.md index 2403d6199..de52765f0 100644 --- a/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/analyze-query-plan.md +++ b/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/analyze-query-plan.md @@ -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: @@ -129,7 +129,7 @@ The following steps set up a Go project using the 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 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/) diff --git a/content/influxdb3/cloud-dedicated/write-data/use-telegraf/configure/_index.md b/content/influxdb3/cloud-dedicated/write-data/use-telegraf/configure/_index.md index f36e6a93b..271f7a7d1 100644 --- a/content/influxdb3/cloud-dedicated/write-data/use-telegraf/configure/_index.md +++ b/content/influxdb3/cloud-dedicated/write-data/use-telegraf/configure/_index.md @@ -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. diff --git a/content/influxdb3/cloud-serverless/_index.md b/content/influxdb3/cloud-serverless/_index.md index 872329f29..06dd1dde3 100644 --- a/content/influxdb3/cloud-serverless/_index.md +++ b/content/influxdb3/cloud-serverless/_index.md @@ -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. Get started with InfluxDB Cloud Serverless -## 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. diff --git a/content/influxdb3/cloud-serverless/admin/billing/limits.md b/content/influxdb3/cloud-serverless/admin/billing/limits.md index a7bbb748b..c0f0039f6 100644 --- a/content/influxdb3/cloud-serverless/admin/billing/limits.md +++ b/content/influxdb3/cloud-serverless/admin/billing/limits.md @@ -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) diff --git a/content/influxdb3/cloud-serverless/admin/buckets/manage-explicit-bucket-schemas.md b/content/influxdb3/cloud-serverless/admin/buckets/manage-explicit-bucket-schemas.md index c6b05e592..99f319322 100644 --- a/content/influxdb3/cloud-serverless/admin/buckets/manage-explicit-bucket-schemas.md +++ b/content/influxdb3/cloud-serverless/admin/buckets/manage-explicit-bucket-schemas.md @@ -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 %}} diff --git a/content/influxdb3/cloud-serverless/get-started/_index.md b/content/influxdb3/cloud-serverless/get-started/_index.md index d047bad0d..19789f2de 100644 --- a/content/influxdb3/cloud-serverless/get-started/_index.md +++ b/content/influxdb3/cloud-serverless/get-started/_index.md @@ -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. | `influxctl` CLI | - | - | - | | [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 %}}. diff --git a/content/influxdb3/cloud-serverless/get-started/query.md b/content/influxdb3/cloud-serverless/get-started/query.md index 93bfb2006..e6df25880 100644 --- a/content/influxdb3/cloud-serverless/get-started/query.md +++ b/content/influxdb3/cloud-serverless/get-started/query.md @@ -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- {{% 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(); diff --git a/content/influxdb3/cloud-serverless/get-started/write.md b/content/influxdb3/cloud-serverless/get-started/write.md index 0399eba37..66ba71149 100644 --- a/content/influxdb3/cloud-serverless/get-started/write.md +++ b/content/influxdb3/cloud-serverless/get-started/write.md @@ -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. @@ -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(); } } diff --git a/content/influxdb3/cloud-serverless/guides/api-compatibility/v2/_index.md b/content/influxdb3/cloud-serverless/guides/api-compatibility/v2/_index.md index 4b8d1f9a3..4fd2bbd9a 100644 --- a/content/influxdb3/cloud-serverless/guides/api-compatibility/v2/_index.md +++ b/content/influxdb3/cloud-serverless/guides/api-compatibility/v2/_index.md @@ -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/) diff --git a/content/influxdb3/cloud-serverless/guides/migrate-data/_index.md b/content/influxdb3/cloud-serverless/guides/migrate-data/_index.md index 82b09863c..edfddd3b4 100644 --- a/content/influxdb3/cloud-serverless/guides/migrate-data/_index.md +++ b/content/influxdb3/cloud-serverless/guides/migrate-data/_index.md @@ -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, diff --git a/content/influxdb3/cloud-serverless/guides/migrate-data/migrate-1x-to-serverless.md b/content/influxdb3/cloud-serverless/guides/migrate-data/migrate-1x-to-serverless.md index ceb70d2d4..e7bdb4649 100644 --- a/content/influxdb3/cloud-serverless/guides/migrate-data/migrate-1x-to-serverless.md +++ b/content/influxdb3/cloud-serverless/guides/migrate-data/migrate-1x-to-serverless.md @@ -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, diff --git a/content/influxdb3/cloud-serverless/guides/migrate-data/migrate-tsm-to-serverless.md b/content/influxdb3/cloud-serverless/guides/migrate-data/migrate-tsm-to-serverless.md index 9596e2f15..1eb518656 100644 --- a/content/influxdb3/cloud-serverless/guides/migrate-data/migrate-tsm-to-serverless.md +++ b/content/influxdb3/cloud-serverless/guides/migrate-data/migrate-tsm-to-serverless.md @@ -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, diff --git a/content/influxdb3/cloud-serverless/guides/prototype-evaluation.md b/content/influxdb3/cloud-serverless/guides/prototype-evaluation.md index 672d78e56..69a7638a6 100644 --- a/content/influxdb3/cloud-serverless/guides/prototype-evaluation.md +++ b/content/influxdb3/cloud-serverless/guides/prototype-evaluation.md @@ -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. diff --git a/content/influxdb3/cloud-serverless/pages.md b/content/influxdb3/cloud-serverless/pages.md index 3581f182a..feed7e459 100644 --- a/content/influxdb3/cloud-serverless/pages.md +++ b/content/influxdb3/cloud-serverless/pages.md @@ -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. diff --git a/content/influxdb3/cloud-serverless/process-data/downsample/client-libraries.md b/content/influxdb3/cloud-serverless/process-data/downsample/client-libraries.md index 5ef7d41e2..876966d6e 100644 --- a/content/influxdb3/cloud-serverless/process-data/downsample/client-libraries.md +++ b/content/influxdb3/cloud-serverless/process-data/downsample/client-libraries.md @@ -17,9 +17,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-serverless/reference/client-libraries/v3/). +[InfluxDB 3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/). This guide also assumes you have already [setup your Python project and virtual environment](/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/python/#create-a-python-virtual-environment). diff --git a/content/influxdb3/cloud-serverless/process-data/downsample/quix.md b/content/influxdb3/cloud-serverless/process-data/downsample/quix.md index 791a84b8c..41d39e7ba 100644 --- a/content/influxdb3/cloud-serverless/process-data/downsample/quix.md +++ b/content/influxdb3/cloud-serverless/process-data/downsample/quix.md @@ -24,9 +24,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-serverless/reference/client-libraries/v3/). +[InfluxDB 3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/). This guide also assumes you have already [setup your Python project and virtual environment](/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/python/#create-a-python-virtual-environment). @@ -211,7 +211,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', diff --git a/content/influxdb3/cloud-serverless/process-data/send-alerts.md b/content/influxdb3/cloud-serverless/process-data/send-alerts.md index 154195b9b..f10966a45 100644 --- a/content/influxdb3/cloud-serverless/process-data/send-alerts.md +++ b/content/influxdb3/cloud-serverless/process-data/send-alerts.md @@ -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-serverless/reference/client-libraries/v3/). +[InfluxDB 3 client libraries](/influxdb3/cloud-serverless/reference/client-libraries/v3/). Whatever clients and platforms you choose the use, the process is the same: #### Alerting process diff --git a/content/influxdb3/cloud-serverless/process-data/tools/pandas.md b/content/influxdb3/cloud-serverless/process-data/tools/pandas.md index 80452582a..6341ad354 100644 --- a/content/influxdb3/cloud-serverless/process-data/tools/pandas.md +++ b/content/influxdb3/cloud-serverless/process-data/tools/pandas.md @@ -50,7 +50,7 @@ stored in an {{% product-name %}} bucket. ## Install prerequisites -The examples in this guide assume using a Python virtual environment and the InfluxDB v3 [`influxdb3-python` Python client library](/influxdb3/cloud-serverless/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-serverless/reference/client-libraries/v3/python/). For more information, see how to [get started using Python to query InfluxDB](/influxdb3/cloud-serverless/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. diff --git a/content/influxdb3/cloud-serverless/process-data/tools/pyarrow.md b/content/influxdb3/cloud-serverless/process-data/tools/pyarrow.md index 79a3eaf6f..f14673a2c 100644 --- a/content/influxdb3/cloud-serverless/process-data/tools/pyarrow.md +++ b/content/influxdb3/cloud-serverless/process-data/tools/pyarrow.md @@ -52,7 +52,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-serverless/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-serverless/reference/client-libraries/v3/python/). For more information, see how to [get started using Python to query InfluxDB](/influxdb3/cloud-serverless/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. diff --git a/content/influxdb3/cloud-serverless/process-data/visualize/chronograf.md b/content/influxdb3/cloud-serverless/process-data/visualize/chronograf.md index 27273a394..99c12cf14 100644 --- a/content/influxdb3/cloud-serverless/process-data/visualize/chronograf.md +++ b/content/influxdb3/cloud-serverless/process-data/visualize/chronograf.md @@ -118,7 +118,7 @@ To complete administrative tasks, use the following: ### 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-serverless/reference/influxql/feature-support/). diff --git a/content/influxdb3/cloud-serverless/process-data/visualize/grafana.md b/content/influxdb3/cloud-serverless/process-data/visualize/grafana.md index 1ce71a8ea..c5dd058fd 100644 --- a/content/influxdb3/cloud-serverless/process-data/visualize/grafana.md +++ b/content/influxdb3/cloud-serverless/process-data/visualize/grafana.md @@ -59,7 +59,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 %}} diff --git a/content/influxdb3/cloud-serverless/query-data/execute-queries/_index.md b/content/influxdb3/cloud-serverless/query-data/execute-queries/_index.md index c38255786..5a6b7e700 100644 --- a/content/influxdb3/cloud-serverless/query-data/execute-queries/_index.md +++ b/content/influxdb3/cloud-serverless/query-data/execute-queries/_index.md @@ -16,7 +16,7 @@ aliases: Use tools and libraries to query data stored in an {{% product-name %}} bucket. -InfluxDB v3 supports the following APIs and languages for querying data: +InfluxDB 3 supports the following APIs and languages for querying data: - Flight+RPC with SQL or InfluxQL. Use InfluxDB client libraries and Flight+RPC clients to query with SQL or InfluxQL and retrieve data in [Arrow in-memory format](https://arrow.apache.org/docs/format/Columnar.html). @@ -26,10 +26,10 @@ InfluxDB v3 supports the following APIs and languages for querying data: Use the `/query` endpoint with InfluxQL and tools such as Telegraf, HTTP clients, and InfluxDB v1 client libraries to query and retrieve data in JSON or CSV format. {{% warn %}} -#### /api/v2/query endpoint can't query InfluxDB v3 +#### /api/v2/query endpoint can't query InfluxDB 3 {{% product-name %}} doesn't support the InfluxDB v2 HTTP `/api/v2/query` endpoint and isn't optimized for the Flux query language. -Use SQL or InfluxQL to query data stored in InfluxDB v3. +Use SQL or InfluxQL to query data stored in InfluxDB 3. {{% /warn %}} Learn how to connect to InfluxDB and query your data using the following tools: diff --git a/content/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/_index.md b/content/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/_index.md index dede94c75..49c53e3ad 100644 --- a/content/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/_index.md +++ b/content/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/_index.md @@ -3,8 +3,8 @@ title: Use InfluxDB client libraries to query data seotitle: 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: @@ -16,8 +16,8 @@ related: - /influxdb3/cloud-serverless/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" >}} diff --git a/content/influxdb3/cloud-serverless/query-data/execute-queries/v1-http.md b/content/influxdb3/cloud-serverless/query-data/execute-queries/v1-http.md index ec9fe396a..1886f3106 100644 --- a/content/influxdb3/cloud-serverless/query-data/execute-queries/v1-http.md +++ b/content/influxdb3/cloud-serverless/query-data/execute-queries/v1-http.md @@ -27,7 +27,7 @@ list_code_example: | --- Use the InfluxDB v1 HTTP API `/query` endpoint and InfluxQL to query data stored in {{< product-name >}} and return results in JSON or CSV format. -The `/query` endpoint provides compatibility for InfluxDB 1.x workloads that you bring to InfluxDB v3. +The `/query` endpoint provides compatibility for InfluxDB 1.x workloads that you bring to InfluxDB 3. _Before you can use the v1 query API, [databases and retention policies must be mapped to buckets](/influxdb3/cloud-serverless/guides/api-compatibility/v1/#map-v1-databases-and-retention-policies-to-buckets)._ diff --git a/content/influxdb3/cloud-serverless/query-data/execute-queries/visualization-tools.md b/content/influxdb3/cloud-serverless/query-data/execute-queries/visualization-tools.md index ca54a0495..bd5bf3e29 100644 --- a/content/influxdb3/cloud-serverless/query-data/execute-queries/visualization-tools.md +++ b/content/influxdb3/cloud-serverless/query-data/execute-queries/visualization-tools.md @@ -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-serverless/reference/influxql/feature-support/). diff --git a/content/influxdb3/cloud-serverless/query-data/influxql/parameterized-queries.md b/content/influxdb3/cloud-serverless/query-data/influxql/parameterized-queries.md index df22c6200..bc72db2e7 100644 --- a/content/influxdb3/cloud-serverless/query-data/influxql/parameterized-queries.md +++ b/content/influxdb3/cloud-serverless/query-data/influxql/parameterized-queries.md @@ -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 %}} bucket 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-serverless/reference/client-libraries/v3/) support parameterized queries. +- Not all [InfluxDB 3 Flight clients](/influxdb3/cloud-serverless/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 diff --git a/content/influxdb3/cloud-serverless/query-data/sql/parameterized-queries.md b/content/influxdb3/cloud-serverless/query-data/sql/parameterized-queries.md index 7a0a31818..0a6bb131c 100644 --- a/content/influxdb3/cloud-serverless/query-data/sql/parameterized-queries.md +++ b/content/influxdb3/cloud-serverless/query-data/sql/parameterized-queries.md @@ -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 %}} bucket 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-serverless/reference/client-libraries/v3/) support parameterized queries. +- Not all [InfluxDB 3 Flight clients](/influxdb3/cloud-serverless/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 diff --git a/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/analyze-query-plan.md b/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/analyze-query-plan.md index 11a27de2b..4cde1781f 100644 --- a/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/analyze-query-plan.md +++ b/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/analyze-query-plan.md @@ -18,7 +18,7 @@ related: Learn how to read and analyze a [query plan](/influxdb3/cloud-serverless/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. @@ -47,7 +47,7 @@ Use the `EXPLAIN` keyword (and the optional [`ANALYZE`](/influxdb3/cloud-serverl {{% 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: @@ -130,7 +130,7 @@ The following steps set up a Go project using the 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/). @@ -149,7 +149,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 @@ -163,7 +163,7 @@ The following steps set up a JavaScript project using the 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/) diff --git a/content/influxdb3/clustered/_index.md b/content/influxdb3/clustered/_index.md index 9fdfd81d3..718c4892b 100644 --- a/content/influxdb3/clustered/_index.md +++ b/content/influxdb3/clustered/_index.md @@ -1,7 +1,7 @@ --- title: InfluxDB Clustered documentation description: > - InfluxDB Clustered is a highly available InfluxDB 3.0 cluster hosted and + InfluxDB Clustered is a highly available InfluxDB 3 cluster hosted and managed on your own infrastructure. The InfluxDB time series platform is designed to handle high write and query loads. Learn how to use and leverage InfluxDB Clustered for your specific @@ -12,7 +12,7 @@ menu: weight: 1 --- -InfluxDB Clustered is a highly available InfluxDB 3.0 cluster hosted and +InfluxDB Clustered is a highly available InfluxDB 3 cluster hosted and managed on your own infrastructure. The InfluxDB time series platform is designed to handle high write and query loads. Learn how to use and leverage InfluxDB Clustered for your specific @@ -21,13 +21,13 @@ time series use case. Contact InfluxData Sales Get started with InfluxDB Clustered -## 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 with it 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" >}} diff --git a/content/influxdb3/clustered/admin/custom-partitions/view-partitions.md b/content/influxdb3/clustered/admin/custom-partitions/view-partitions.md index 1572d551d..10de04c08 100644 --- a/content/influxdb3/clustered/admin/custom-partitions/view-partitions.md +++ b/content/influxdb3/clustered/admin/custom-partitions/view-partitions.md @@ -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_clustered: diff --git a/content/influxdb3/clustered/admin/databases/create.md b/content/influxdb3/clustered/admin/databases/create.md index 442259812..7bdc4c602 100644 --- a/content/influxdb3/clustered/admin/databases/create.md +++ b/content/influxdb3/clustered/admin/databases/create.md @@ -222,7 +222,7 @@ threshold beyond which query performance may be affected {{< 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. diff --git a/content/influxdb3/clustered/admin/env-vars.md b/content/influxdb3/clustered/admin/env-vars.md index c714da7d0..75defd836 100644 --- a/content/influxdb3/clustered/admin/env-vars.md +++ b/content/influxdb3/clustered/admin/env-vars.md @@ -89,8 +89,8 @@ components: {{% /code-tab-content %}} {{< /code-tabs-wrapper >}} -_For more information about components in the InfluxDB v3 storage engine, see -the [InfluxDB v3 storage engine architecture](/influxdb3/clustered/reference/internals/storage-engine/)._ +_For more information about components in the InfluxDB 3 storage engine, see +the [InfluxDB 3 storage engine architecture](/influxdb3/clustered/reference/internals/storage-engine/)._ ## Set environment variables for a component diff --git a/content/influxdb3/clustered/admin/query-system-data.md b/content/influxdb3/clustered/admin/query-system-data.md index fea3f36ab..5ed427ba1 100644 --- a/content/influxdb3/clustered/admin/query-system-data.md +++ b/content/influxdb3/clustered/admin/query-system-data.md @@ -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. @@ -403,7 +403,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). diff --git a/content/influxdb3/clustered/admin/tables/create.md b/content/influxdb3/clustered/admin/tables/create.md index 41514196e..98a77855f 100644 --- a/content/influxdb3/clustered/admin/tables/create.md +++ b/content/influxdb3/clustered/admin/tables/create.md @@ -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. diff --git a/content/influxdb3/clustered/get-started/_index.md b/content/influxdb3/clustered/get-started/_index.md index 97eb8fea1..7e464a5d7 100644 --- a/content/influxdb3/clustered/get-started/_index.md +++ b/content/influxdb3/clustered/get-started/_index.md @@ -12,7 +12,7 @@ influxdb3/clustered/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 @@ This tutorial covers many of the recommended tools. | [`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" >}}** | | InfluxDB user interface | - | - | - | -| [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/clustered/reference/client-libraries/v2/) | - | **{{< icon "check" >}}** | - | | [InfluxDB v1 client libraries](/influxdb3/clustered/reference/client-libraries/v1/) | - | **{{< icon "check" >}}** | **{{< icon "check" >}}** | | [Telegraf](/telegraf/v1/){{< req text="\* " color="magenta" >}} | - | **{{< icon "check" >}}** | - | @@ -151,7 +151,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/clustered/reference/client-libraries/v3/) are the recommended client libraries for writing and querying data {{% product-name %}}. +[InfluxDB 3 client libraries](/influxdb3/clustered/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. [InfluxDB v2 client libraries](/influxdb3/clustered/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 %}}. diff --git a/content/influxdb3/clustered/get-started/query.md b/content/influxdb3/clustered/get-started/query.md index fee19a772..697618535 100644 --- a/content/influxdb3/clustered/get-started/query.md +++ b/content/influxdb3/clustered/get-started/query.md @@ -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/clustered/reference/client-libraries/v3/){{< req text="\* " color="magenta" >}} +- [InfluxDB 3 client libraries](/influxdb3/clustered/reference/client-libraries/v3/){{< req text="\* " color="magenta" >}} - [Flight clients](/influxdb3/clustered/reference/client-libraries/flight/) - [Superset](/influxdb3/clustered/query-data/sql/execute-queries/superset/) - [Grafana](/influxdb3/clustered/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/clustered/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. {{% 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/clustered/get-started/write/?t=Python#write-line-protocol-to-influxdb). @@ -1049,7 +1049,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(); diff --git a/content/influxdb3/clustered/get-started/write.md b/content/influxdb3/clustered/get-started/write.md index f90a64b52..e659cc608 100644 --- a/content/influxdb3/clustered/get-started/write.md +++ b/content/influxdb3/clustered/get-started/write.md @@ -797,7 +797,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 @@ -1201,7 +1201,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. @@ -1441,7 +1441,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 @@ -1563,7 +1563,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(); } } diff --git a/content/influxdb3/clustered/guides/api-compatibility/v1/_index.md b/content/influxdb3/clustered/guides/api-compatibility/v1/_index.md index 8435a5674..e4cfc421e 100644 --- a/content/influxdb3/clustered/guides/api-compatibility/v1/_index.md +++ b/content/influxdb3/clustered/guides/api-compatibility/v1/_index.md @@ -325,7 +325,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. @@ -442,7 +442,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/clustered/reference/client-libraries/v3/) +- [InfluxDB 3 client libraries](/influxdb3/clustered/reference/client-libraries/v3/) - [Flight clients](/influxdb3/clustered/reference/client-libraries/flight/) - [Superset](/influxdb3/clustered/query-data/sql/execute-queries/superset/) - [Grafana](/influxdb3/clustered/query-data/sql/execute-queries/grafana/) diff --git a/content/influxdb3/clustered/guides/api-compatibility/v2/_index.md b/content/influxdb3/clustered/guides/api-compatibility/v2/_index.md index 996528676..4053bd071 100644 --- a/content/influxdb3/clustered/guides/api-compatibility/v2/_index.md +++ b/content/influxdb3/clustered/guides/api-compatibility/v2/_index.md @@ -228,7 +228,7 @@ To setup and start using client libraries, see the [Get started](/influxdb3/clus {{% 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/clustered/reference/client-libraries/v3/) +- [InfluxDB 3 client libraries](/influxdb3/clustered/reference/client-libraries/v3/) - [Flight clients](/influxdb3/clustered/reference/client-libraries/flight/) - [Superset](/influxdb3/clustered/query-data/sql/execute-queries/superset/) - [Grafana](/influxdb3/clustered/query-data/sql/execute-queries/grafana/) diff --git a/content/influxdb3/clustered/guides/migrate-data/_index.md b/content/influxdb3/clustered/guides/migrate-data/_index.md index 1ebd5fcf7..180c64828 100644 --- a/content/influxdb3/clustered/guides/migrate-data/_index.md +++ b/content/influxdb3/clustered/guides/migrate-data/_index.md @@ -12,7 +12,7 @@ alt_links: cloud: /influxdb/cloud/write-data/migrate-data/ --- -Migrate data to InfluxDB Clustered powered by InfluxDB v3 from other +Migrate data to InfluxDB Clustered powered by InfluxDB 3 from other InfluxDB instances powered by TSM including InfluxDB OSS 1.x, 2.x, InfluxDB Enterprise, and InfluxDB Cloud (TSM). @@ -35,7 +35,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? @@ -51,7 +51,7 @@ series data with SQL. For more information about querying your data with SQL, se **Yes, you should migrate**. One of the primary goals when designing the InfluxDB v3 storage engine was to enable performant implementations of both SQL and InfluxQL. When compared to querying InfluxDB powered by TSM (InfluxDB OSS 1.x, 2.x, and Enterprise), -InfluxQL queries are more performant when querying InfluxDB powered by InfluxDB v3. +InfluxQL queries are more performant when querying InfluxDB powered by InfluxDB 3. #### Are you reliant on Flux queries and Flux tasks? @@ -63,7 +63,7 @@ InfluxQL queries are more performant when querying InfluxDB powered by InfluxDB 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 diff --git a/content/influxdb3/clustered/guides/migrate-data/migrate-1x-to-clustered.md b/content/influxdb3/clustered/guides/migrate-data/migrate-1x-to-clustered.md index e9c43bfba..7abec4490 100644 --- a/content/influxdb3/clustered/guides/migrate-data/migrate-1x-to-clustered.md +++ b/content/influxdb3/clustered/guides/migrate-data/migrate-1x-to-clustered.md @@ -34,7 +34,7 @@ export the data as line protocol and write the exported data to an InfluxDB data 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 diff --git a/content/influxdb3/clustered/guides/migrate-data/migrate-tsm-to-clustered.md b/content/influxdb3/clustered/guides/migrate-data/migrate-tsm-to-clustered.md index 4209b4ce4..f644ed803 100644 --- a/content/influxdb3/clustered/guides/migrate-data/migrate-tsm-to-clustered.md +++ b/content/influxdb3/clustered/guides/migrate-data/migrate-tsm-to-clustered.md @@ -3,7 +3,7 @@ title: Migrate data from InfluxDB Cloud to InfluxDB Clustered description: > To migrate data from a TSM-powered InfluxDB Cloud to InfluxDB Clustered 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 InfluxDB cluster. + the queried data to an InfluxDB 3 database in your InfluxDB cluster. menu: influxdb3_clustered: name: Migrate from TSM to Clustered @@ -24,7 +24,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] @@ -43,7 +43,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 diff --git a/content/influxdb3/clustered/install/_index.md b/content/influxdb3/clustered/install/_index.md index 5d215ee72..a82f80870 100644 --- a/content/influxdb3/clustered/install/_index.md +++ b/content/influxdb3/clustered/install/_index.md @@ -54,13 +54,13 @@ Updating your InfluxDB cluster is as simple as re-applying your app-instance wit The word safely here means being able to redeploy your cluster while still being able to use the tokens you’ve created, and being able to write/query to the database you’ve previously created. -All of the important state in Influxdb 3.0 lives in the Catalog (the Postgres equivalent database) and the Object Store (the S3 compatible store). These should be treated with the utmost care. +All of the important state in InfluxDB 3 lives in the Catalog (the Postgres equivalent database) and the Object Store (the S3 compatible store). These should be treated with the utmost care. If a full redeploy of your cluster needs to happen, the namespace containing the Influxdb instance can be deleted **_as long as your Catalog and Object Store are not in this namespace_**. Then, the influxdb AppInstance can be redeployed. It is possible the operator may need to be removed and reinstalled. In that case, deleting the namespace that the operator is deployed into and redeploying is acceptable. ### Backing up your data -The Catalog and Object store contain all of the important state for Influxdb 3.0. They should be the primary focus of backups. Following the industry standard best practices for your chosen Catalog implementation and Object Store implementation should provide sufficient backups. In our Cloud products, we do daily backups of our Catalog, in addition to automatic snapshots, and we preserve our Object Store files for 100 days after they have been soft-deleted. +The Catalog and Object store contain all of the important state for InfluxDB 3. They should be the primary focus of backups. Following the industry standard best practices for your chosen Catalog implementation and Object Store implementation should provide sufficient backups. In our Cloud products, we do daily backups of our Catalog, in addition to automatic snapshots, and we preserve our Object Store files for 100 days after they have been soft-deleted. ### Recovering your data diff --git a/content/influxdb3/clustered/install/optimize-cluster/write-methods.md b/content/influxdb3/clustered/install/optimize-cluster/write-methods.md index fd1b933ff..a094657a5 100644 --- a/content/influxdb3/clustered/install/optimize-cluster/write-methods.md +++ b/content/influxdb3/clustered/install/optimize-cluster/write-methods.md @@ -65,7 +65,7 @@ same client library to write data to your cluster. -- [InfluxDB v3 client libraries](/influxdb3/clustered/reference/client-libraries/v3/) +- [InfluxDB 3 client libraries](/influxdb3/clustered/reference/client-libraries/v3/) - [C# .NET](/influxdb3/clustered/reference/client-libraries/v3/csharp/) - [Go](/influxdb3/clustered/reference/client-libraries/v3/go/) - [Java](/influxdb3/clustered/reference/client-libraries/v3/java/) diff --git a/content/influxdb3/clustered/pages.md b/content/influxdb3/clustered/pages.md index 3581f182a..feed7e459 100644 --- a/content/influxdb3/clustered/pages.md +++ b/content/influxdb3/clustered/pages.md @@ -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. diff --git a/content/influxdb3/clustered/process-data/downsample/downsample-client-libraries.md b/content/influxdb3/clustered/process-data/downsample/downsample-client-libraries.md index 9fc110645..fe3b75210 100644 --- a/content/influxdb3/clustered/process-data/downsample/downsample-client-libraries.md +++ b/content/influxdb3/clustered/process-data/downsample/downsample-client-libraries.md @@ -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/clustered/reference/client-libraries/v3/). +[InfluxDB 3 client libraries](/influxdb3/clustered/reference/client-libraries/v3/). This guide also assumes you have already [setup your Python project and virtual environment](/influxdb3/clustered/query-data/execute-queries/client-libraries/python/#create-a-python-virtual-environment). diff --git a/content/influxdb3/clustered/process-data/downsample/quix.md b/content/influxdb3/clustered/process-data/downsample/quix.md index a62781f43..b26fa2a92 100644 --- a/content/influxdb3/clustered/process-data/downsample/quix.md +++ b/content/influxdb3/clustered/process-data/downsample/quix.md @@ -24,9 +24,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/clustered/reference/client-libraries/v3/). +[InfluxDB 3 client libraries](/influxdb3/clustered/reference/client-libraries/v3/). This guide also assumes you have already [setup your Python project and virtual environment](/influxdb3/clustered/query-data/execute-queries/client-libraries/python/#create-a-python-virtual-environment). @@ -211,7 +211,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', diff --git a/content/influxdb3/clustered/process-data/send-alerts.md b/content/influxdb3/clustered/process-data/send-alerts.md index a2f8eeb1f..62f010ba5 100644 --- a/content/influxdb3/clustered/process-data/send-alerts.md +++ b/content/influxdb3/clustered/process-data/send-alerts.md @@ -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/clustered/reference/client-libraries/v3/). +[InfluxDB 3 client libraries](/influxdb3/clustered/reference/client-libraries/v3/). Whatever clients and platforms you choose the use, the process is the same: #### Alerting process diff --git a/content/influxdb3/clustered/process-data/tools/pandas.md b/content/influxdb3/clustered/process-data/tools/pandas.md index 7c659e4f3..c895f28aa 100644 --- a/content/influxdb3/clustered/process-data/tools/pandas.md +++ b/content/influxdb3/clustered/process-data/tools/pandas.md @@ -51,7 +51,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/clustered/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/clustered/reference/client-libraries/v3/python/). For more information, see how to [get started using Python to query InfluxDB](/influxdb3/clustered/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. diff --git a/content/influxdb3/clustered/process-data/tools/pyarrow.md b/content/influxdb3/clustered/process-data/tools/pyarrow.md index 900e50626..b0462d005 100644 --- a/content/influxdb3/clustered/process-data/tools/pyarrow.md +++ b/content/influxdb3/clustered/process-data/tools/pyarrow.md @@ -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/clustered/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/clustered/reference/client-libraries/v3/python/). For more information, see how to [get started using Python to query InfluxDB](/influxdb3/clustered/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. diff --git a/content/influxdb3/clustered/process-data/visualize/chronograf.md b/content/influxdb3/clustered/process-data/visualize/chronograf.md index 4a9f7500e..150b23cc4 100644 --- a/content/influxdb3/clustered/process-data/visualize/chronograf.md +++ b/content/influxdb3/clustered/process-data/visualize/chronograf.md @@ -123,7 +123,7 @@ To complete [administrative tasks](/influxdb3/clustered/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/clustered/reference/influxql/feature-support/). diff --git a/content/influxdb3/clustered/process-data/visualize/grafana.md b/content/influxdb3/clustered/process-data/visualize/grafana.md index 3d18a863d..0c56cfca6 100644 --- a/content/influxdb3/clustered/process-data/visualize/grafana.md +++ b/content/influxdb3/clustered/process-data/visualize/grafana.md @@ -54,7 +54,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 %}} diff --git a/content/influxdb3/clustered/query-data/execute-queries/client-libraries/_index.md b/content/influxdb3/clustered/query-data/execute-queries/client-libraries/_index.md index 036606f31..a18ff5c54 100644 --- a/content/influxdb3/clustered/query-data/execute-queries/client-libraries/_index.md +++ b/content/influxdb3/clustered/query-data/execute-queries/client-libraries/_index.md @@ -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/clustered/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" >}} diff --git a/content/influxdb3/clustered/query-data/execute-queries/influxdb-v1-api.md b/content/influxdb3/clustered/query-data/execute-queries/influxdb-v1-api.md index 07b83db82..9f1104c84 100644 --- a/content/influxdb3/clustered/query-data/execute-queries/influxdb-v1-api.md +++ b/content/influxdb3/clustered/query-data/execute-queries/influxdb-v1-api.md @@ -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/clustered/reference/influxql/feature-support/). diff --git a/content/influxdb3/clustered/query-data/execute-queries/visualization-tools.md b/content/influxdb3/clustered/query-data/execute-queries/visualization-tools.md index c7ec5612a..15d19a1cf 100644 --- a/content/influxdb3/clustered/query-data/execute-queries/visualization-tools.md +++ b/content/influxdb3/clustered/query-data/execute-queries/visualization-tools.md @@ -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/clustered/reference/influxql/feature-support/). diff --git a/content/influxdb3/clustered/query-data/influxql/parameterized-queries.md b/content/influxdb3/clustered/query-data/influxql/parameterized-queries.md index 453e96263..01cf7fcbc 100644 --- a/content/influxdb3/clustered/query-data/influxql/parameterized-queries.md +++ b/content/influxdb3/clustered/query-data/influxql/parameterized-queries.md @@ -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/clustered/reference/client-libraries/v3/) support parameterized queries. +- Not all [InfluxDB 3 Flight clients](/influxdb3/clustered/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 diff --git a/content/influxdb3/clustered/query-data/sql/parameterized-queries.md b/content/influxdb3/clustered/query-data/sql/parameterized-queries.md index 48cafdc0a..8fc0fa870 100644 --- a/content/influxdb3/clustered/query-data/sql/parameterized-queries.md +++ b/content/influxdb3/clustered/query-data/sql/parameterized-queries.md @@ -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/clustered/reference/client-libraries/v3/) support parameterized queries. +- Not all [InfluxDB 3 Flight clients](/influxdb3/clustered/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 diff --git a/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/analyze-query-plan.md b/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/analyze-query-plan.md index 2e2ff299e..7e2d67274 100644 --- a/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/analyze-query-plan.md +++ b/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/analyze-query-plan.md @@ -19,7 +19,7 @@ related: Learn how to read and analyze a [query plan](/influxdb3/clustered/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/clustered/ref {{% 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: @@ -130,7 +130,7 @@ The following steps set up a Go project using the 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/). @@ -149,7 +149,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 @@ -163,7 +163,7 @@ The following steps set up a JavaScript project using the 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/) diff --git a/content/influxdb3/clustered/write-data/use-telegraf/configure/_index.md b/content/influxdb3/clustered/write-data/use-telegraf/configure/_index.md index 89c3c7ab0..38118e586 100644 --- a/content/influxdb3/clustered/write-data/use-telegraf/configure/_index.md +++ b/content/influxdb3/clustered/write-data/use-telegraf/configure/_index.md @@ -121,7 +121,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. diff --git a/content/influxdb3/core/_index.md b/content/influxdb3/core/_index.md index c762ae3ca..c29a5e204 100644 --- a/content/influxdb3/core/_index.md +++ b/content/influxdb3/core/_index.md @@ -3,7 +3,7 @@ title: InfluxDB 3 Core documentation description: > InfluxDB 3 Core is an open source time series database designed and optimized for real-time and recent data. - Learn how to use and leverage InfluxDB v3 in use cases such as edge data + Learn how to use and leverage InfluxDB 3 in use cases such as edge data collection, IoT data, and events. menu: influxdb3_core: diff --git a/content/influxdb3/core/reference/influxql/feature-support.md b/content/influxdb3/core/reference/influxql/feature-support.md index f054676b6..5aa3a5936 100644 --- a/content/influxdb3/core/reference/influxql/feature-support.md +++ b/content/influxdb3/core/reference/influxql/feature-support.md @@ -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. diff --git a/content/influxdb3/enterprise/reference/influxql/feature-support.md b/content/influxdb3/enterprise/reference/influxql/feature-support.md index b0a4ffc4f..a10c90e97 100644 --- a/content/influxdb3/enterprise/reference/influxql/feature-support.md +++ b/content/influxdb3/enterprise/reference/influxql/feature-support.md @@ -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. diff --git a/content/shared/influxql-v3-reference/_index.md b/content/shared/influxql-v3-reference/_index.md index cb9cf4b35..2d92d8bf2 100644 --- a/content/shared/influxql-v3-reference/_index.md +++ b/content/shared/influxql-v3-reference/_index.md @@ -4,7 +4,7 @@ with InfluxDB and work with times series data. > [!Important] > #### 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](/influxdb/version/reference/influxql/feature-support/). diff --git a/content/shared/influxql-v3-reference/feature-support.md b/content/shared/influxql-v3-reference/feature-support.md index 3d6d5f48b..feacf93fa 100644 --- a/content/shared/influxql-v3-reference/feature-support.md +++ b/content/shared/influxql-v3-reference/feature-support.md @@ -1,4 +1,4 @@ -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. This page provides information about the current implementation status of InfluxQL features. @@ -56,9 +56,9 @@ The following table provides information about what metaqueries are available in > > #### Cardinality metaqueries > -> With the InfluxDB v3 storage engine, series cardinality is no longer a limiting +> With the InfluxDB 3 storage engine, series cardinality is no longer a limiting > factor for database performance. -> Cardinality-related metaqueries will likely not be supported with the InfluxDB v3 +> Cardinality-related metaqueries will likely not be supported with the InfluxDB 3 > storage engine. ## Function support diff --git a/content/shared/influxql-v3-reference/functions/_index.md b/content/shared/influxql-v3-reference/functions/_index.md index c0407a364..64e136ed3 100644 --- a/content/shared/influxql-v3-reference/functions/_index.md +++ b/content/shared/influxql-v3-reference/functions/_index.md @@ -5,7 +5,7 @@ Use InfluxQL functions to aggregate, select, transform, analyze, and predict dat > #### Missing InfluxQL functions > > Some InfluxQL functions are in the process of being rearchitected to work with -> the InfluxDB v3 storage engine. If a function you need is not here, check the +> the InfluxDB 3 storage engine. If a function you need is not here, check the > [InfluxQL feature support page](/influxdb/version/reference/influxql/feature-support/#function-support) > for more information. diff --git a/content/shared/influxql-v3-reference/functions/aggregates.md b/content/shared/influxql-v3-reference/functions/aggregates.md index 0895aa0cf..c4c2ecc4e 100644 --- a/content/shared/influxql-v3-reference/functions/aggregates.md +++ b/content/shared/influxql-v3-reference/functions/aggregates.md @@ -20,7 +20,7 @@ _Examples use the sample data set provided in the > #### Missing InfluxQL functions > > Some InfluxQL functions are in the process of being rearchitected to work with -> the InfluxDB v3 storage engine. If a function you need is not here, check the +> the InfluxDB 3 storage engine. If a function you need is not here, check the > [InfluxQL feature support page](/influxdb/version/reference/influxql/feature-support/#function-support) > for more information. diff --git a/content/shared/influxql-v3-reference/functions/selectors.md b/content/shared/influxql-v3-reference/functions/selectors.md index ac5bf7bbf..7c29cd797 100644 --- a/content/shared/influxql-v3-reference/functions/selectors.md +++ b/content/shared/influxql-v3-reference/functions/selectors.md @@ -20,7 +20,7 @@ _Examples use the sample data set provided in the > #### Missing InfluxQL functions > > Some InfluxQL functions are in the process of being rearchitected to work with -> the InfluxDB v3 storage engine. If a function you need is not here, check the +> the InfluxDB 3 storage engine. If a function you need is not here, check the > [InfluxQL feature support page](/influxdb/version/reference/influxql/feature-support/#function-support) > for more information. diff --git a/content/shared/influxql-v3-reference/functions/transformations.md b/content/shared/influxql-v3-reference/functions/transformations.md index 96b22a20f..466c22843 100644 --- a/content/shared/influxql-v3-reference/functions/transformations.md +++ b/content/shared/influxql-v3-reference/functions/transformations.md @@ -31,7 +31,7 @@ InfluxQL transformation functions modify and return values in each row of querie > #### Missing InfluxQL functions > > Some InfluxQL functions are in the process of being rearchitected to work with -> the InfluxDB v3 storage engine. If a function you need is not here, check the +> the InfluxDB 3 storage engine. If a function you need is not here, check the > [InfluxQL feature support page](/influxdb/version/reference/influxql/feature-support/#function-support) > for more information. diff --git a/content/shared/influxql-v3-reference/limit-and-slimit.md b/content/shared/influxql-v3-reference/limit-and-slimit.md index 3b3ffae34..29b6a737e 100644 --- a/content/shared/influxql-v3-reference/limit-and-slimit.md +++ b/content/shared/influxql-v3-reference/limit-and-slimit.md @@ -104,7 +104,7 @@ tags: room=Living Room ## SLIMIT clause > [!Important] -> 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, such as `SLIMIT` are still > being implemented. For more information, see > [InfluxQL feature support](/influxdb/version/reference/influxql/feature-support/). diff --git a/content/shared/influxql-v3-reference/offset-and-soffset.md b/content/shared/influxql-v3-reference/offset-and-soffset.md index 2df0fe35b..1954e0138 100644 --- a/content/shared/influxql-v3-reference/offset-and-soffset.md +++ b/content/shared/influxql-v3-reference/offset-and-soffset.md @@ -128,7 +128,7 @@ tags: room=Living Room ## `SOFFSET` clause > [!Important] -> 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, such as `SOFFSET` are still > being implemented. For more information, see > [InfluxQL feature support](/influxdb/version/reference/influxql/feature-support/). diff --git a/content/shared/v3-distributed-admin-custom-partitions/_index.md b/content/shared/v3-distributed-admin-custom-partitions/_index.md index 3f4a82508..cfd360979 100644 --- a/content/shared/v3-distributed-admin-custom-partitions/_index.md +++ b/content/shared/v3-distributed-admin-custom-partitions/_index.md @@ -1,4 +1,4 @@ -When writing data to {{< product-name >}}, the InfluxDB v3 storage engine stores data in [Apache Parquet](https://parquet.apache.org/) format in the [Object store](/influxdb/version/reference/internals/storage-engine/#object-store). Each Parquet file represents a _partition_--a logical grouping of data. +When writing data to {{< product-name >}}, the InfluxDB 3 storage engine stores data in [Apache Parquet](https://parquet.apache.org/) format in the [Object store](/influxdb/version/reference/internals/storage-engine/#object-store). Each Parquet file represents a _partition_--a logical grouping of data. By default, InfluxDB partitions each table _by day_. If this default strategy yields unsatisfactory performance for single-series queries, you can define a custom partitioning strategy by specifying tag values and different time intervals to optimize query performance for your specific schema and workload. @@ -40,7 +40,7 @@ storage structure to improve query performance specific to your schema and workl ## Disadvantages Using custom partitioning may increase the load on other parts of the -[InfluxDB v3 storage engine](/influxdb/version/reference/internals/storage-engine/), +[InfluxDB 3 storage engine](/influxdb/version/reference/internals/storage-engine/), but you can scale each part individually to address the added load. {{% note %}} @@ -329,7 +329,7 @@ The faster the query engine can identify what partitions to read and then read the data in those partitions, the more performant queries are. _For more information about the query lifecycle, see -[InfluxDB v3 query life cycle](/influxdb/version/reference/internals/storage-engine/#query-life-cycle)._ +[InfluxDB 3 query life cycle](/influxdb/version/reference/internals/storage-engine/#query-life-cycle)._ ##### Query example diff --git a/content/shared/v3-distributed-admin-custom-partitions/view-partitions.md b/content/shared/v3-distributed-admin-custom-partitions/view-partitions.md index f0097583f..d3e4e311c 100644 --- a/content/shared/v3-distributed-admin-custom-partitions/view-partitions.md +++ b/content/shared/v3-distributed-admin-custom-partitions/view-partitions.md @@ -1,5 +1,5 @@ -{{< product-name >}} stores partition information in InfluxDB v3 system tables. +{{< product-name >}} stores partition information in InfluxDB 3 system tables. Query partition information to view partition templates and verify partitions are working as intended. @@ -9,7 +9,7 @@ are working as intended. {{% warn %}} #### Querying system tables may impact overall cluster performance -Partition information is stored in InfluxDB v3 system tables. +Partition information is stored in InfluxDB 3 system tables. Querying system tables may impact the overall write and query performance of your {{< product-name omit=" Clustered" >}} cluster.