update shared links to use ambiguous version

Author: sanderson

content/shared/influxql-v3-reference/time-and-timezone.md

@@ -65,7 +65,7 @@ updated timestamp.
 ## Query time range
 
 To specify the time range of a query, use conditional expressions in the
-[`WHERE` clause](/influxdb/cloud-dedicated/reference/influxql/where/) that
+[`WHERE` clause](/influxdb/version/reference/influxql/where/) that
 compare the value of the `time` column to an absolute timestamp or a relative
 timestamp.
 

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/cloud-dedicated/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 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.
 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.
@@ -20,8 +20,8 @@ you can define a custom partitioning strategy by specifying tag values and diffe
 >
 > Consider custom partitioning if:
 > 
-> 1. You have taken steps to [optimize your queries](/influxdb/cloud-dedicated/query-data/troubleshoot-and-optimize/optimize-queries/), and
-> 2. Performance for _single-series queries_ (querying for a specific [tag value](/influxdb/cloud-dedicated/reference/glossary/#tag-value) or [tag set](/influxdb/cloud-dedicated/reference/glossary/#tag-set)) is still unsatisfactory. 
+> 1. You have taken steps to [optimize your queries](/influxdb/version/query-data/troubleshoot-and-optimize/optimize-queries/), and
+> 2. Performance for _single-series queries_ (querying for a specific [tag value](/influxdb/version/reference/glossary/#tag-value) or [tag set](/influxdb/version/reference/glossary/#tag-set)) is still unsatisfactory. 
 > 
 > Before choosing a partitioning strategy, weigh the [advantages](#advantages), [disadvantages](#disadvantages), and [limitations](#limitations) of custom partitioning.
 
@@ -40,21 +40,21 @@ 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/cloud-dedicated/reference/internals/storage-engine/),
+[InfluxDB v3 storage engine](/influxdb/version/reference/internals/storage-engine/),
 but you can scale each part individually to address the added load.
 
 {{% note %}}
 _The weight of these disadvantages depends upon the cardinality of
  tags and the specificity of time intervals used for partitioning._
 {{% /note %}}
 
-- **Increased load on the [Ingester](/influxdb/cloud-dedicated/reference/internals/storage-engine/#ingester)**
+- **Increased load on the [Ingester](/influxdb/version/reference/internals/storage-engine/#ingester)**
   as it groups data into smaller partitions and files.
-- **Increased load on the [Catalog](/influxdb/cloud-dedicated/reference/internals/storage-engine/#catalog)**
+- **Increased load on the [Catalog](/influxdb/version/reference/internals/storage-engine/#catalog)**
   as more references to partition Parquet file locations are stored and queried.
-- **Increased load on the [Compactor](/influxdb/cloud-dedicated/reference/internals/storage-engine/#compactor)**
+- **Increased load on the [Compactor](/influxdb/version/reference/internals/storage-engine/#compactor)**
   as it needs to compact more partition Parquet files.
-- **Increased costs associated with [Object storage](/influxdb/cloud-dedicated/reference/internals/storage-engine/#object-storage)**
+- **Increased costs associated with [Object storage](/influxdb/version/reference/internals/storage-engine/#object-storage)**
   as more partition Parquet files are created and stored.
 - **Increased latency**. The amount of time for InfluxDB to process a query and return results increases linearly, although slightly, with the total partition count for a table.
 - **Risk of decreased performance for queries that don't use tags in the WHERE clause**.
@@ -74,10 +74,10 @@ After you have considered the [advantages](#advantages), [disadvantages](#disadv
 custom partitioning, use the guides in this section to:
 
 1. Learn [how partitioning works](#how-partitioning-works)
-2. Follow [best practices](/influxdb/cloud-dedicated/admin/custom-partitions/best-practices/) for defining partitions and managing partition
+2. Follow [best practices](/influxdb/version/admin/custom-partitions/best-practices/) for defining partitions and managing partition
    growth
-3. [Define custom partitions](/influxdb/cloud-dedicated/admin/custom-partitions/define-custom-partitions/) for your data
-4. Take steps to [limit the number of partition files](/influxdb/cloud-dedicated/admin/custom-partitions/best-practices/#limit-the-number-of-partition-files)
+3. [Define custom partitions](/influxdb/version/admin/custom-partitions/define-custom-partitions/) for your data
+4. Take steps to [limit the number of partition files](/influxdb/version/admin/custom-partitions/best-practices/#limit-the-number-of-partition-files)
 
 ## How partitioning works
 
@@ -88,7 +88,7 @@ and determines the time interval that InfluxDB partitions data by.
 Partition templates use tag values and
 [Rust strftime date and time formatting syntax](https://docs.rs/chrono/latest/chrono/format/strftime/index.html).
 
-_For more detailed information, see [Partition templates](/influxdb/cloud-dedicated/admin/custom-partitions/partition-templates/)._
+_For more detailed information, see [Partition templates](/influxdb/version/admin/custom-partitions/partition-templates/)._
 
 ### Partition keys
 
@@ -319,8 +319,8 @@ production,line=B,station=wld temp=106.5,qty=43i 1704070800000000000
 
 When querying data:
 
-1.  The [Catalog](/influxdb/cloud-dedicated/reference/internals/storage-engine/#catalog)
-    provides the v3 query engine ([Querier](/influxdb/cloud-dedicated/reference/internals/storage-engine/#querier))
+1.  The [Catalog](/influxdb/version/reference/internals/storage-engine/#catalog)
+    provides the v3 query engine ([Querier](/influxdb/version/reference/internals/storage-engine/#querier))
     with the locations of partitions that contain the queried time series data.
 2.  The query engine reads all rows in the returned partitions to identify what
     rows match the logic in the query and should be included in the query result.
@@ -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/cloud-dedicated/reference/internals/storage-engine/#query-life-cycle)._
+[InfluxDB v3 query life cycle](/influxdb/version/reference/internals/storage-engine/#query-life-cycle)._
 
 ##### Query example
 

content/shared/v3-distributed-admin-custom-partitions/best-practices.md

@@ -21,7 +21,7 @@ query engine to more quickly identify what partitions contain the relevant data.
 
 Partitioning using distinct values of tags with many (10K+) unique values can
 actually hurt query performance as partitions are created for each unique tag value.
-Instead, use [tag buckets](/influxdb/cloud-dedicated/admin/custom-partitions/partition-templates/#tag-bucket-part-templates)
+Instead, use [tag buckets](/influxdb/version/admin/custom-partitions/partition-templates/#tag-bucket-part-templates)
 to partition by high-cardinality tags.
 This method of partitioning groups tag values into "buckets" and partitions by bucket.
 {{% /note %}}
@@ -33,7 +33,7 @@ If points don't have a value for the tag, InfluxDB can't store them in the corre
 
 ## Avoid over-partitioning
 
-As you plan your partitioning strategy, keep in mind that over-partitioning your data can hurt query performance. If partitions are too granular, queries may need to retrieve and read many partitions from the [Object store](/influxdb/cloud-dedicated/reference/internals/storage-engine/#object-store).
+As you plan your partitioning strategy, keep in mind that over-partitioning your data can hurt query performance. If partitions are too granular, queries may need to retrieve and read many partitions from the [Object store](/influxdb/version/reference/internals/storage-engine/#object-store).
 
 - Balance the partition time interval with the actual amount of data written during each interval. If a single interval doesn't contain a lot of data, partition by larger time intervals.
 - Avoid partitioning by tags that you typically don't use in your query workload.
@@ -49,7 +49,7 @@ partition count.
 We currently recommend planning to keep the total partition count below 10,000.
 
 - [Estimate the total partition count](#estimate-the-total-partition-count) for the lifespan of your data
-- **Set a [database retention period](/influxdb/cloud-dedicated/admin/databases/#retention-period)**
+- **Set a [database retention period](/influxdb/version/admin/databases/#retention-period)**
   to prevent the number of partitions from growing unbounded
 - **Partition by month or year** to [avoid over-partitioning](#avoid-over-partitioning)
 - **Don't partition on high cardinality tags** unless you also use [tag buckets](#use-tag-buckets-for-high-cardinality-tags)
@@ -63,7 +63,7 @@ lifetime of the database (or retention period):
 total_partition_count = (cardinality_of_partitioned_tag) * (data_lifespan / partition_duration)
 ```
 
-- `total_partition_count`: The number of partition files in [Object storage](/influxdb/cloud-dedicated/reference/internals/storage-engine/#object-storage)
+- `total_partition_count`: The number of partition files in [Object storage](/influxdb/version/reference/internals/storage-engine/#object-storage)
 - `cardinality_of_partitioned_tag`: The number of distinct values for a tag
-- `data_lifespan`: The [database retention period](/influxdb/cloud-dedicated/admin/databases/#retention-period), if set, or the expected lifetime of the database
-- `partition_duration`: The partition time interval, defined by the [time part template](/influxdb/cloud-dedicated/admin/custom-partitions/partition-templates/#time-part-templates)
+- `data_lifespan`: The [database retention period](/influxdb/version/admin/databases/#retention-period), if set, or the expected lifetime of the database
+- `partition_duration`: The partition time interval, defined by the [time part template](/influxdb/version/admin/custom-partitions/partition-templates/#time-part-templates)

content/shared/v3-distributed-admin-custom-partitions/define-custom-partitions.md

@@ -1,10 +1,10 @@
-Use the [`influxctl` CLI](/influxdb/cloud-dedicated/reference/cli/influxctl/)
+Use the [`influxctl` CLI](/influxdb/version/reference/cli/influxctl/)
 to define custom partition strategies when creating a database or table.
 By default, {{< product-name >}} partitions data by day.
 
 The partitioning strategy of a database or table is determined by a
-[partition template](/influxdb/cloud-dedicated/admin/custom-partitions/#partition-templates)
-which defines the naming pattern for [partition keys](/influxdb/cloud-dedicated/admin/custom-partitions/#partition-keys).
+[partition template](/influxdb/version/admin/custom-partitions/#partition-templates)
+which defines the naming pattern for [partition keys](/influxdb/version/admin/custom-partitions/#partition-keys).
 Partition keys uniquely identify each partition.
 When a partition template is applied to a database, it becomes the default template
 for all tables in that database, but can be overridden when creating a
@@ -23,15 +23,15 @@ You can't update a partition template on an existing resource.
 {{% /warn %}}
 
 Use the following command flags to identify
-[partition template parts](/influxdb/cloud-dedicated/admin/custom-partitions/partition-templates/#tag-part-templates):
+[partition template parts](/influxdb/version/admin/custom-partitions/partition-templates/#tag-part-templates):
 
-- `--template-tag`: An [InfluxDB tag](/influxdb/cloud-dedicated/reference/glossary/#tag)
+- `--template-tag`: An [InfluxDB tag](/influxdb/version/reference/glossary/#tag)
   to use in the partition template.
-- `--template-tag-bucket`: An [InfluxDB tag](/influxdb/cloud-dedicated/reference/glossary/#tag)
+- `--template-tag-bucket`: An [InfluxDB tag](/influxdb/version/reference/glossary/#tag)
   and number of "buckets" to group tag values into.
   Provide the tag key and the number of buckets to bucket tag values into
   separated by a comma: `tagKey,N`.
-- `--template-timeformat`: A [Rust strftime date and time](/influxdb/cloud-dedicated/admin/custom-partitions/partition-templates/#time-part-templates)
+- `--template-timeformat`: A [Rust strftime date and time](/influxdb/version/admin/custom-partitions/partition-templates/#time-part-templates)
   string that specifies the time format in the partition template and determines
   the time interval to partition by.
 
@@ -40,7 +40,7 @@ A partition template can include up to 7 total tag and tag bucket parts
 and only 1 time part.
 {{% /note %}}
 
-_View [partition template part restrictions](/influxdb/cloud-dedicated/admin/custom-partitions/partition-templates/#restrictions)._
+_View [partition template part restrictions](/influxdb/version/admin/custom-partitions/partition-templates/#restrictions)._
 
 {{% note %}}
 #### Always provide a time format when using custom partitioning
@@ -95,7 +95,7 @@ influxctl table create \
 
 Replace the following in your command:
 
-- {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}: your {{% product-name %}} [database](/influxdb/cloud-dedicated/admin/databases/)
+- {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}: your {{% product-name %}} [database](/influxdb/version/admin/databases/)
 
 <!--actual test
 
@@ -127,7 +127,7 @@ rm /shared/temp_tables.txt
 
 ## Example partition templates
 
-Given the following [line protocol](/influxdb/cloud-dedicated/reference/syntax/line-protocol/)
+Given the following [line protocol](/influxdb/version/reference/syntax/line-protocol/)
 with a `2024-01-01T00:00:00Z` timestamp:
 
 ```text

content/shared/v3-distributed-admin-custom-partitions/partition-templates.md

@@ -1,13 +1,13 @@
 Use partition templates to define the patterns used to generate partition keys.
 A partition key uniquely identifies a partition and is used to name the partition
-Parquet file in the [Object store](/influxdb/cloud-dedicated/reference/internals/storage-engine/#object-store).
+Parquet file in the [Object store](/influxdb/version/reference/internals/storage-engine/#object-store).
 
 A partition template consists of 1-8 _template parts_---dimensions to partition data by.
 Three types of template parts exist:
 
-- **tag**: An [InfluxDB tag](/influxdb/cloud-dedicated/reference/glossary/#tag)
+- **tag**: An [InfluxDB tag](/influxdb/version/reference/glossary/#tag)
   to partition by.
-- **tag bucket**: An [InfluxDB tag](/influxdb/cloud-dedicated/reference/glossary/#tag)
+- **tag bucket**: An [InfluxDB tag](/influxdb/version/reference/glossary/#tag)
   and number of "buckets" to group tag values into. Data is partitioned by the
   tag bucket rather than each distinct tag value.
 - {{< req type="key" >}} **time**: A Rust strftime date and time string that specifies the time interval

content/shared/v3-distributed-admin-custom-partitions/view-partitions.md

@@ -28,18 +28,18 @@ If you detect a schema change or a non-functioning query example, please
 
 ## Query partition information from system tables
 
-Use the [`influxctl query` command](/influxdb/cloud-dedicated/reference/cli/influxctl/query/)
+Use the [`influxctl query` command](/influxdb/version/reference/cli/influxctl/query/)
 and SQL to query partition-related information from InfluxDB system tables.
  Provide the following:
 
 - **Enable system tables** with the `--enable-system-tables` command flag.
-- **Database token**: A [database token](/influxdb/cloud-dedicated/admin/tokens/#database-tokens)
+- **Database token**: A [database token](/influxdb/version/admin/tokens/#database-tokens)
   with read permissions on the specified database. Uses the `token` setting from
-  the [`influxctl` connection profile](/influxdb/cloud-dedicated/reference/cli/influxctl/#configure-connection-profiles)
+  the [`influxctl` connection profile](/influxdb/version/reference/cli/influxctl/#configure-connection-profiles)
   or the `--token` command flag.
 - **Database name**: The name of the database to query information about.
   Uses the `database` setting from the
-  [`influxctl` connection profile](/influxdb/cloud-dedicated/reference/cli/influxctl/#configure-connection-profiles)
+  [`influxctl` connection profile](/influxdb/version/reference/cli/influxctl/#configure-connection-profiles)
   or the `--database` command flag.
 - **SQL query**: The SQL query to execute.
   Pass the query in one of the following ways: