Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update mentions of IOx to v3 (#5256) 

* update mentions of IOx to v3

* Apply suggestions from code review

Co-authored-by: Jason Stirnaman <stirnamanj@gmail.com>

---------

Co-authored-by: Jason Stirnaman <stirnamanj@gmail.com>
pull/5259/head
Scott Anderson 2023-11-30 11:52:40 -07:00 committed by GitHub
parent df791ea56e
commit cbd2a0b72a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
41 changed files with 81 additions and 79 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
assets/js/influxdb-url.js
View File

@ -16,7 +16,7 @@ var elementSelector = ".article--content pre:not(.preserve)"
// Return the page context (cloud, oss/enterprise, dedicated, clustered, other)
function context() {
if (/\/influxdb\/cloud(?:-iox)/.test(window.location.pathname)) {
if (/\/influxdb\/cloud(?:-serverless)/.test(window.location.pathname)) {
return "cloud"
} else if (/\/influxdb\/cloud-dedicated/.test(window.location.pathname)) {
return "dedicated"

2
content/influxdb/cloud-dedicated/guides/migrate-data/_index.md
View File

@ -50,7 +50,7 @@ series data with SQL. For more information about querying your data with SQL, se
#### Do you want better InfluxQL performance?
**Yes, you should migrate**. One of the primary goals when designing the InfluxDB
IOx storage engine was to enable performant implementations of both SQL and InfluxQL.
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 the v3 storage engine.

2
content/influxdb/cloud-dedicated/process-data/visualize/chronograf.md
View File

@ -123,7 +123,7 @@ To complete [administrative tasks](/influxdb/cloud-dedicated/admin/), use the
### Limited InfluxQL feature support
InfluxQL is being rearchitected to work with the InfluxDB IOx storage engine.
InfluxQL is being rearchitected to work with the InfluxDB v3 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/cloud-dedicated/reference/influxql/feature-support/).

2
content/influxdb/cloud-dedicated/process-data/visualize/superset.md
View File

@ -212,7 +212,7 @@ With Superset running, you're ready to [log in](#log-in-to-superset) and set up
{{< img-hd src="/img/influxdb/cloud-serverless-superset-connect.png" alt="Configure InfluxDB connection in Superset" />}}
4. Enter a **Display Name** (for example, _InfluxDB Cloud IOx_) for the database connection.
4. Enter a **Display Name** (for example, _InfluxDB Cloud Dedicated_) for the database connection.
5. Enter your **SQL Alchemy URI** comprised of the following:
- **Protocol**: `datafusion+flightsql`

2
content/influxdb/cloud-dedicated/query-data/execute-queries/influxdb-v1-api.md
View File

@ -34,7 +34,7 @@ but you can use any HTTP client.
{{% warn %}}
#### InfluxQL feature support
InfluxQL is being rearchitected to work with the InfluxDB IOx storage engine.
InfluxQL is being rearchitected to work with the InfluxDB v3 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/cloud-dedicated/reference/influxql/feature-support/).

2
content/influxdb/cloud-dedicated/query-data/execute-queries/visualization-tools.md
View File

@ -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 IOx storage engine.
InfluxQL is being rearchitected to work with the InfluxDB v3 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/cloud-dedicated/reference/influxql/feature-support/).

4
content/influxdb/cloud-dedicated/reference/client-libraries/v3/go.md
View File

@ -108,7 +108,7 @@ Replace the following configuration values:
### Function `Client.Query()`
Query data from InfluxDB IOx using SQL.
Query data from InfluxDB v3 using SQL.
#### Syntax
@ -143,7 +143,7 @@ iterator, err := client.Query(context.Background(), query)
### Function `Client.QueryWithOptions()`
Query data from InfluxDB IOx with query options such as **query type** for querying with InfluxQL.
Query data from InfluxDB v3 with query options such as **query type** for querying with InfluxQL.
#### Syntax

9
content/influxdb/cloud-dedicated/reference/glossary.md
View File

@ -123,7 +123,7 @@ CSV file format is not fully standardized.
Cardinality is the number of unique values in a set.
Series cardinality is the number of unique [series](#series) in a database as a whole.
With the IOx storage engine, high series cardinality _does not_ affect performance.
With the InfluxDB v3 storage engine, high series cardinality _does not_ affect performance.
### cluster
@ -463,8 +463,9 @@ Related entries:
### IOx
The IOx storage engine is real-time, columnar database optimized for time series
data built in Rust on top of [Apache Arrow](https://arrow.apache.org/) and
The IOx storage engine (InfluxDB v3 storage engine) is a real-time, columnar
database optimized for time series data built in Rust on top of
[Apache Arrow](https://arrow.apache.org/) and
[DataFusion](https://arrow.apache.org/datafusion/user-guide/introduction.html).
IOx replaces the [TSM](#tsm) storage engine.
@ -1021,7 +1022,7 @@ Related entries:
The InfluxDB v1 and v2 data storage format that allows greater compaction and
higher write and read throughput than B+ or LSM tree implementations.
The TSM storage engine has been replaced by [IOx](#iox).
The TSM storage engine has been replaced by the [InfluxDB v3 storage engine (IOx)](#iox).
Related entries:
[IOx](#iox)

2
content/influxdb/cloud-dedicated/reference/internals/security.md
View File

@ -82,7 +82,7 @@ and protected in its own virtual private cloud (VPC).
Users interact with InfluxDB Cloud Dedicated only through Cloud Dedicated established APIs.
For cluster management activities, authorized users interact with the Granite service.
For workload clusters, authorized users interact with APIs for IOx Ingesters (writes) and IOx Queriers (reads).
For workload clusters, authorized users interact with APIs for InfluxDB v3 Ingesters (writes) and Queriers (reads).
These services don't expose AWS S3 or other cloud provider or internal services.
InfluxDB Cloud Dedicated uses separate S3 buckets for each customer's cluster to persist writes.
The S3 buckets are only accessible by the customer's cluster services.

6
content/influxdb/cloud-dedicated/write-data/best-practices/schema-design.md
View File

@ -125,15 +125,15 @@ The following guidelines help to optimize query performance:
### Avoid wide schemas
A wide schema is one with many tags and fields and corresponding columns for each.
With the InfluxDB IOx storage engine, wide schemas don't impact query execution performance.
Because IOx is a columnar database, it executes queries only against columns selected in the query.
With the InfluxDB v3 storage engine, wide schemas don't impact query execution performance.
Because v3 is a columnar database, it executes queries only against columns selected in the query.
Although a wide schema won't affect query performance, it can lead to the following:
- More resources required for persisting and compacting data during ingestion.
- Decreased sorting performance due to complex primary keys with [too many tags](#avoid-too-many-tags).
The InfluxDB IOx storage engine has a
The InfluxDB v3 storage engine has a
[limit of 250 columns per measurement](#measurements-can-contain-up-to-250-columns).
To avoid a wide schema, limit the number of tags and fields stored in a measurement.

2
content/influxdb/cloud-dedicated/write-data/csv/telegraf.md
View File

@ -144,5 +144,5 @@ data to InfluxDB.
The preceding examples describe Telegraf configurations necessary for writing to {{% product-name %}}.
The output plugin provides several other options for configuring the Telegraf client:
- `influx_uint_support`: supported by the InfluxDB IOx storage engine.
- `influx_uint_support`: supported by the InfluxDB v3 storage engine.
- See [`influxdb_v2` plugin options](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb_v2/README.md) on GitHub.

2
content/influxdb/cloud-dedicated/write-data/use-telegraf/configure/_index.md
View File

@ -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 IOx.
`influx_uint_support`: supported in InfluxDB v3.
For more plugin options, see [`influxdb`](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb/README.md) on GitHub.

6
content/influxdb/cloud-serverless/_index.md
View File

@ -1,8 +1,8 @@
---
title: InfluxDB Cloud Serverless documentation
description: >
InfluxDB Cloud Serverless is a hosted and managed version of InfluxDB backed
by InfluxDB IOx, the time series platform designed to handle high write and query loads.
InfluxDB Cloud Serverless is a hosted and managed version of InfluxDB v3, 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.
menu:
@ -14,7 +14,7 @@ weight: 1
{{% note %}}
This InfluxDB Cloud documentation applies to all [organizations](/influxdb/cloud-serverless/admin/organizations/) created through
**cloud2.influxdata.com** on or after **January 31, 2023** that are powered by
the InfluxDB IOx storage engine. If your organization was created before this
the InfluxDB v3 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/).

5
content/influxdb/cloud-serverless/admin/billing/limits.md
View File

@ -55,7 +55,8 @@ InfluxDB Cloud Serverless has adjustable service quotas applied per account.
### Storage-level
The InfluxDB IOx storage engine enforces limits on the storage level that apply to all accounts (Free Plan and Usage-Based Plan).
The InfluxDB v3 storage engine enforces limits on the storage level that apply
to all accounts (Free Plan and Usage-Based Plan).
- [Terminology](#terminology)
- [Service-level limits](#limits)
@ -68,7 +69,7 @@ The InfluxDB IOx storage engine enforces limits on the storage level that apply
#### Storage-level limits
The IOx storage engine enforces the following storage-level limits:
The v3 storage engine enforces the following storage-level limits:
- **Maximum number of tables per namespace**: 500
- **Maximum number of columns per table**: 200

2
content/influxdb/cloud-serverless/guides/api-compatibility/v1/_index.md
View File

@ -331,7 +331,7 @@ Replace the following:
##### Other Telegraf configuration options
`influx_uint_support`: supported in InfluxDB IOx.
`influx_uint_support`: supported in InfluxDB v3.
For more plugin options, see [`influxdb`](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb/README.md) on GitHub.

18
content/influxdb/cloud-serverless/guides/migrate-data/_index.md
View File

@ -38,8 +38,8 @@ 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 IOx storage engine supports near limitless series cardinality and is without
question, the better solution for high series cardinality workloads.
The InfluxDB v3 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?
@ -52,7 +52,7 @@ series data with SQL. For more information about querying your data with SQL, se
<!-- #### Do you want better InfluxQL performance?
**Yes, you should migrate**. One of the primary goals when designing the InfluxDB
IOx storage engine was to enable performant implementations of both SQL and InfluxQL.
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 the v3 storage engine. -->
@ -63,16 +63,16 @@ 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 IOx storage engine is available in a region that meets your requirements.
We are currently working to make InfluxDB IOx available on more providers and
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
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 IOx
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 IOx.
**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.
---

8
content/influxdb/cloud-serverless/guides/migrate-data/migrate-tsm-to-serverless.md
View File

@ -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 IOx bucket in your
time-based batches and write the queried data to an InfluxDB v3 bucket in your
InfluxDB Cloud Serverless organization.
menu:
influxdb_cloud_serverless:
@ -26,8 +26,8 @@ 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 IOx-powered bucket in another
organization.
and writes each batch to an InfluxDB Cloud Serverless (InfluxDB v3) bucket in
another organization.
{{% cloud %}}
All query and write requests are subject to your InfluxDB Cloud organization's
@ -119,7 +119,7 @@ import "date"
import "influxdata/influxdb/secrets"
// Configure the task
option task = {every: 5m, name: "Migrate data from TSM to IOx"}
option task = {every: 5m, name: "Migrate data from TSM to v3"}
// Configure the migration
migration = {

2
content/influxdb/cloud-serverless/process-data/visualize/chronograf.md
View File

@ -118,7 +118,7 @@ To complete administrative tasks, use the following:
### Limited InfluxQL feature support
InfluxQL is being rearchitected to work with the InfluxDB IOx storage engine.
InfluxQL is being rearchitected to work with the InfluxDB v3 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/cloud-serverless/reference/influxql/feature-support/).

2
content/influxdb/cloud-serverless/query-data/execute-queries/influxdb-v1-api.md
View File

@ -43,7 +43,7 @@ For more information, see
{{% warn %}}
#### InfluxQL feature support
InfluxQL is being rearchitected to work with the InfluxDB IOx storage engine.
InfluxQL is being rearchitected to work with the InfluxDB v3 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/cloud-serverless/reference/influxql/feature-support/).

2
content/influxdb/cloud-serverless/query-data/execute-queries/visualization-tools.md
View File

@ -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 IOx storage engine.
InfluxQL is being rearchitected to work with the InfluxDB v3 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/cloud-serverless/reference/influxql/feature-support/).

2
content/influxdb/cloud-serverless/reference/cli/influx/apply/_index.md
View File

@ -20,7 +20,7 @@ metadata: [influx CLI 2.0.0+]
While this command is included in the `influx` CLI {{< latest-cli >}}, this
functionality is not available in InfluxDB Cloud Serverless organizations
powered by the InfluxDB IOx storage engine.
powered by the InfluxDB v3 storage engine.
{{% /warn %}}
{{< duplicate-oss >}}

2
content/influxdb/cloud-serverless/reference/cli/influx/dashboards/_index.md
View File

@ -19,7 +19,7 @@ metadata: [influx CLI 2.0.0+]
While this command is included in the `influx` CLI {{< latest-cli >}}, this
functionality is not available in InfluxDB Cloud Serverless organizations
powered by the InfluxDB IOx storage engine.
powered by the InfluxDB v3 storage engine.
{{% /warn %}}
{{< duplicate-oss >}}

2
content/influxdb/cloud-serverless/reference/cli/influx/export/_index.md
View File

@ -17,7 +17,7 @@ cascade:
While this command is included in the `influx` CLI , this
functionality is not available in InfluxDB Cloud Serverless organizations
powered by the InfluxDB IOx storage engine.
powered by the InfluxDB v3 storage engine.
---
{{< duplicate-oss >}}

4
content/influxdb/cloud-serverless/reference/client-libraries/v3/go.md
View File

@ -109,7 +109,7 @@ Replace the following configuration values:
### Function `Client.Query()`
Query data from InfluxDB IOx using SQL.
Query data from InfluxDB v3 using SQL.
#### Syntax
@ -144,7 +144,7 @@ iterator, err := client.Query(context.Background(), query)
### Function `Client.QueryWithOptions()`
Query data from InfluxDB IOx with query options such as **query type** for querying with InfluxQL.
Query data from InfluxDB v3 with query options such as **query type** for querying with InfluxQL.
#### Syntax

8
content/influxdb/cloud-serverless/reference/glossary.md
View File

@ -125,7 +125,7 @@ CSV file format is not fully standardized.
Cardinality is the number of unique values in a set.
Series cardinality is the number of unique [series](#series) in a bucket as a whole.
With the IOx storage engine, high series cardinality _does not_ affect performance.
With the InfluxDB v3 storage engine, high series cardinality _does not_ affect performance.
### cluster
@ -470,7 +470,7 @@ Related entries:
### IOx
The IOx storage engine is real-time, columnar database optimized for time series
The IOx (InfluxDB v3) storage engine is a real-time, columnar database optimized for time series
data built in Rust on top of [Apache Arrow](https://arrow.apache.org/) and
[DataFusion](https://arrow.apache.org/datafusion/user-guide/introduction.html).
IOx replaces the [TSM](#tsm) storage engine.
@ -665,7 +665,7 @@ Related entries:
### primary key
With the InfluxDB IOx storage engine, the primary key is the list of columns
With the InfluxDB v3 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.
A row's primary key tag set does not include tags with null values.
@ -1024,7 +1024,7 @@ Related entries:
The InfluxDB v1 and v2 data storage format that allows greater compaction and
higher write and read throughput than B+ or LSM tree implementations.
The TSM storage engine has been replaced by [IOx](#iox).
The TSM storage engine has been replaced by [the InfluxDB v3 storage engine (IOx)](#iox).
Related entries:
[IOx](#iox)

6
content/influxdb/cloud-serverless/reference/regions.md
View File

@ -21,15 +21,15 @@ Use the URLs below to interact with your InfluxDB Cloud Serverless instances wit
[Telegraf](/influxdb/cloud-serverless/write-data/use-telegraf/).
{{% note %}}
#### InfluxDB IOx-enabled cloud regions
#### InfluxDB v3 cloud regions
We are in the process of deploying and enabling the InfluxDB IOx storage engine
We are in the process of deploying and enabling the InfluxDB v3 storage engine
on other cloud providers and regions.
{{% /note %}}
<a href="https://www.influxdata.com/influxdb-cloud-2-0-provider-region/" target="_blank" class="btn">Request a cloud region</a>
<!-- ** Uncomment this when we add an IOx region with multiple clusters **
<!-- ** Uncomment this when we add a v3 region with multiple clusters **
{{% note %}}
#### Regions with multiple clusters

6
content/influxdb/cloud-serverless/write-data/best-practices/schema-design.md
View File

@ -125,15 +125,15 @@ The following guidelines help to optimize query performance:
### Avoid wide schemas
A wide schema is one with many tags and fields and corresponding columns for each.
With the InfluxDB IOx storage engine, wide schemas don't impact query execution performance.
Because IOx is a columnar database, it executes queries only against columns selected in the query.
With the InfluxDB v3 storage engine, wide schemas don't impact query execution performance.
Because InfluxDB v3 is a columnar database, it executes queries only against columns selected in the query.
Although a wide schema won't affect query performance, it can lead to the following:
- More resources required for persisting and compacting data during ingestion.
- Decreased sorting performance due to complex primary keys with [too many tags](#avoid-too-many-tags).
The InfluxDB IOx storage engine has a
The InfluxDB v3 storage engine has a
[limit of 200 columns per measurement](#measurements-can-contain-up-to-200-columns).
To avoid a wide schema, limit the number of tags and fields stored in a measurement.

2
content/influxdb/cloud-serverless/write-data/csv/telegraf.md
View File

@ -144,5 +144,5 @@ data to InfluxDB.
The preceding examples describe Telegraf configurations necessary for writing to {{% product-name %}}.
The output plugin provides several other options for configuring the Telegraf client:
- `influx_uint_support`: supported by the InfluxDB IOx storage engine.
- `influx_uint_support`: supported by the InfluxDB v3 storage engine.
- See [`influxdb_v2` plugin options](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb_v2/README.md) on GitHub.

2
content/influxdb/cloud/account-management/switch-org.md
View File

@ -26,7 +26,7 @@ To switch {{< product-name "short" >}} organizations:
#### Migrate to InfluxDB Cloud Serverless
To unlock the benefits of the InfluxDB v3 storage engine, including unlimited
cardinality and SQL, [migrate your data to an InfluxDB Cloud Serverless organization](/influxdb/cloud-serverless/write-data/migrate-data/migrate-tsm-to-iox/).
cardinality and SQL, [migrate your data to an InfluxDB Cloud Serverless organization](/influxdb/cloud-serverless/write-data/migrate-data/migrate-tsm-to-serverless/).
All InfluxDB Cloud [accounts](/influxdb/cloud-serverless/admin/accounts/) and
[organizations](/influxdb/cloud-serverless/admin/organizations/) created through

2
content/influxdb/clustered/guides/api-compatibility/v1/_index.md
View File

@ -325,7 +325,7 @@ Replace the following:
##### Other Telegraf configuration options
`influx_uint_support`: supported in InfluxDB IOx.
`influx_uint_support`: supported in InfluxDB v3.
For more plugin options, see [`influxdb`](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb/README.md) on GitHub.

10
content/influxdb/clustered/guides/migrate-data/_index.md
View File

@ -12,7 +12,7 @@ alt_links:
cloud: /influxdb/cloud/write-data/migrate-data/
---
Migrate data to InfluxDB Clustered powered by InfluxDB IOx from other
Migrate data to InfluxDB Clustered powered by InfluxDB v3 from other
InfluxDB instances powered by TSM including InfluxDB OSS 1.x, 2.x,
InfluxDB Enterprise, and InfluxDB Cloud (TSM).
@ -34,8 +34,8 @@ 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 IOx storage engine supports near limitless series cardinality and is, without
question, the better solution for high series cardinality workloads.
The InfluxDB v3 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?
@ -48,9 +48,9 @@ series data with SQL. For more information about querying your data with SQL, se
#### Do you want better InfluxQL performance?
**Yes, you should migrate**. One of the primary goals when designing the InfluxDB
IOx storage engine was to enable performant implementations of both SQL and InfluxQL.
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 IOx.
InfluxQL queries are more performant when querying InfluxDB powered by InfluxDB v3.
#### Are you reliant on Flux queries and Flux tasks?

2
content/influxdb/clustered/process-data/visualize/chronograf.md
View File

@ -123,7 +123,7 @@ To complete [administrative tasks](/influxdb/clustered/admin/), use the
### Limited InfluxQL feature support
InfluxQL is being rearchitected to work with the InfluxDB IOx storage engine.
InfluxQL is being rearchitected to work with the InfluxDB v3 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/clustered/reference/influxql/feature-support/).

2
content/influxdb/clustered/query-data/execute-queries/influxdb-v1-api.md
View File

@ -34,7 +34,7 @@ but you can use any HTTP client.
{{% warn %}}
#### InfluxQL feature support
InfluxQL is being rearchitected to work with the InfluxDB IOx storage engine.
InfluxQL is being rearchitected to work with the InfluxDB v3 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/clustered/reference/influxql/feature-support/).

2
content/influxdb/clustered/query-data/execute-queries/visualization-tools.md
View File

@ -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 IOx storage engine.
InfluxQL is being rearchitected to work with the InfluxDB v3 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/clustered/reference/influxql/feature-support/).

4
content/influxdb/clustered/reference/client-libraries/v3/go.md
View File

@ -108,7 +108,7 @@ Replace the following configuration values:
### Function `Client.Query()`
Query data from InfluxDB IOx using SQL.
Query data from InfluxDB v3 using SQL.
#### Syntax
@ -143,7 +143,7 @@ iterator, err := client.Query(context.Background(), query)
### Function `Client.QueryWithOptions()`
Query data from InfluxDB IOx with query options such as **query type** for querying with InfluxQL.
Query data from InfluxDB v3 with query options such as **query type** for querying with InfluxQL.
#### Syntax

8
content/influxdb/clustered/reference/glossary.md
View File

@ -123,7 +123,7 @@ CSV file format is not fully standardized.
Cardinality is the number of unique values in a set.
Series cardinality is the number of unique [series](#series) in a database as a whole.
With the IOx storage engine, high series cardinality _does not_ affect performance.
With the InfluxDB v3 storage engine, high series cardinality _does not_ affect performance.
### cluster
@ -463,7 +463,7 @@ Related entries:
### IOx
The IOx storage engine is real-time, columnar database optimized for time series
The IOx (InfluxDB v3) storage engine is real-time, columnar database optimized for time series
data built in Rust on top of [Apache Arrow](https://arrow.apache.org/) and
[DataFusion](https://arrow.apache.org/datafusion/user-guide/introduction.html).
IOx replaces the [TSM](#tsm) storage engine.
@ -658,7 +658,7 @@ Related entries:
### primary key
With the InfluxDB IOx storage engine, the primary key is the list of columns
With the InfluxDB v3 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.
A row's primary key tag set does not include tags with null values.
@ -1021,7 +1021,7 @@ Related entries:
The InfluxDB v1 and v2 data storage format that allows greater compaction and
higher write and read throughput than B+ or LSM tree implementations.
The TSM storage engine has been replaced by [IOx](#iox).
The TSM storage engine has been replaced by [the InfluxDB v3 storage engine (IOx)](#iox).
Related entries:
[IOx](#iox)

2
content/influxdb/clustered/reference/influxql/functions/_index.md
View File

@ -16,7 +16,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 IOx storage engine. If a function you need is not here, check the
the InfluxDB v3 storage engine. If a function you need is not here, check the
[InfluxQL feature support page](/influxdb/clustered/reference/influxql/feature-support/#function-support)
for more information.
{{% /note %}}

6
content/influxdb/clustered/write-data/best-practices/schema-design.md
View File

@ -125,15 +125,15 @@ The following guidelines help to optimize query performance:
### Avoid wide schemas
A wide schema is one with many tags and fields and corresponding columns for each.
With the InfluxDB IOx storage engine, wide schemas don't impact query execution performance.
Because IOx is a columnar database, it executes queries only against columns selected in the query.
With the InfluxDB v3 storage engine, wide schemas don't impact query execution performance.
Because InfluxDB v3 is a columnar database, it executes queries only against columns selected in the query.
Although a wide schema won't affect query performance, it can lead to the following:
- More resources required for persisting and compacting data during ingestion.
- Decreased sorting performance due to complex primary keys with [too many tags](#avoid-too-many-tags).
The InfluxDB IOx storage engine has a
The InfluxDB v3 storage engine has a
[limit of 250 columns per measurement](#measurements-can-contain-up-to-250-columns).
To avoid a wide schema, limit the number of tags and fields stored in a measurement.

2
content/influxdb/clustered/write-data/csv/telegraf.md
View File

@ -144,5 +144,5 @@ data to InfluxDB.
The preceding examples describe Telegraf configurations necessary for writing to {{% product-name %}}.
The output plugin provides several other options for configuring the Telegraf client:
- `influx_uint_support`: supported by the InfluxDB IOx storage engine.
- `influx_uint_support`: supported by the InfluxDB v3 storage engine.
- See [`influxdb_v2` plugin options](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb_v2/README.md) on GitHub.

2
content/influxdb/clustered/write-data/use-telegraf/configure/_index.md
View File

@ -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 IOx.
`influx_uint_support`: supported in InfluxDB v3.
For more plugin options, see [`influxdb`](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/influxdb/README.md) on GitHub.

2
content/influxdb/v2/reference/glossary.md
View File

@ -763,7 +763,7 @@ Related entries: [measurement](#measurement), [tag set](#tag-set), [field set](#
### primary key
With the InfluxDB IOx storage engine, the primary key is the list of columns
With the InfluxDB v3 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.