Manually review content that still mentions v22.2 in 23.1 docs after bump-major-version script

Open

#16,201 opened on Feb 7, 2023 0 comments 0 reactions 1 assignee Claimed by @mikeCRL View on GitHub

Dominant language: HTML
Stars: 212
Forks: 476
Avg merge: 40m
Merged PRs (30d): 3

Description

```
/Users/ml/go/src/github.com/cockroachdb/docs/_includes/v23.1/backups/updated-backup-privileges.md:2
Starting in v22.2, CockroachDB introduces a new [system-level privilege model](security-reference/authorization.html#system-level-privileges) that provides finer control over a user's privilege to work with the database, including taking and managing backups.

/Users/ml/go/src/github.com/cockroachdb/docs/_includes/v23.1/backups/updated-backup-privileges.md:4
There is continued support for the [legacy privilege model](#required-privileges-using-the-legacy-privilege-model) for backups in v22.2, however it **will be removed** in a future release of CockroachDB. We recommend implementing the new privilege model that follows in this section for all new and existing backups.

/Users/ml/go/src/github.com/cockroachdb/docs/_includes/v23.1/backward-incompatible/alpha.1.md:10
- The `GRANT` privilege has been removed and replaced by the more granular [`WITH GRANT OPTION`](../v22.2/grant.html#grant-privileges-with-the-option-to-grant-to-others), which provides control over which privileges are allowed to be granted. [#81310][#81310]

/Users/ml/go/src/github.com/cockroachdb/docs/_includes/v23.1/backward-incompatible/alpha.1.md:15
- Changed the default value of the `enable_implicit_transaction_for_batch_statements` to `true`. This means that a [batch of statements](../v22.2/transactions.html#batched-statements) sent in one string separated by semicolons is treated as an implicit transaction. [#76834][#76834]

/Users/ml/go/src/github.com/cockroachdb/docs/_includes/v23.1/cdc/privilege-model.md:2
Starting in v22.2, CockroachDB introduces a new [system-level privilege model](security-reference/authorization.html#system-level-privileges) that provides finer control over a user's privilege to work with the database, including creating and managing changefeeds.

/Users/ml/go/src/github.com/cockroachdb/docs/_includes/v23.1/cdc/privilege-model.md:4
There is continued support for the [legacy privilege model](#legacy-privilege-model) for changefeeds in v22.2, however it **will be removed** in a future release of CockroachDB. We recommend implementing the new privilege model that follows in this section for all changefeeds.

/Users/ml/go/src/github.com/cockroachdb/docs/_includes/v23.1/misc/session-vars.md:6
| `copy_from_atomic_enabled` | If set to `on`, [`COPY FROM`](copy-from.html) statements are committed atomically, matching PostgreSQL behavior. If set to `off`, `COPY FROM` statements are segmented into batches of 100 rows unless issued within an explicit transaction, matching the CockroachDB behavior in versions prior to v22.2. | `on` | Yes | Yes |

/Users/ml/go/src/github.com/cockroachdb/docs/_includes/v23.1/sql/row-level-ttl-prefer-ttl-expiration-expressions.md:1
Starting with CockroachDB v22.2, we recommend that most users use `ttl_expiration_expression` over `ttl_expire_after` for the following reasons:

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/aws-dms.md:175
This is resolved in v22.2.1. On earlier versions, do not select the **Enable validation** option if your database has a `TIMESTAMP`/`TIMESTAMPTZ` column.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/backup.md:54
The following details the legacy privilege model that CockroachDB supports in v22.2 and earlier. Support for this privilege model will be removed in a future release of CockroachDB:

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/cloud-storage-authentication.md:78
CockroachDB supports assume role authentication on clusters running v22.2. Authenticating to cloud storage with `ASSUME_ROLE` on clusters running versions v22.1 and earlier, or mixed versions, is not supported and will result in failed bulk operations.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/cloud-storage-authentication.md:394
CockroachDB supports assume role authentication on clusters running v22.2. Authenticating to cloud storage with `ASSUME_ROLE` on clusters running versions v22.1 and earlier, or mixed versions, is not supported and will result in failed bulk operations.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/cluster-setup-troubleshooting.md:572
- **A node's disk stalls.** A [disk stall](#disk-stalls) on a node can cause write operations to stall indefinitely, also causes the node's heartbeats to fail since the storage engine cannot write to disk as part of the heartbeat, and may cause read requests to fail if they are waiting for a conflicting write to complete. Lease acquisition from this node can stall indefinitely until the node is shut down or recovered. Pebble detects most stalls and will terminate the `cockroach` process after 20 seconds, but there are gaps in its detection. In v22.1.2+ and v22.2+, each lease acquisition attempt on an unresponsive node times out after 6 seconds. However, CockroachDB can still appear to stall as these timeouts are occurring.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/configure-logs.md:540
Both [Fluentd-compatible](#output-to-fluentd-compatible-network-collectors) and [HTTP](#output-to-http-network-collectors) log sinks support the buffering of log messages by default. Previous to version v22.2, log buffering was only available for the [log file](#output-to-files) log sink.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/create-schedule-for-backup.md:24
The following details the legacy privilege model that CockroachDB supports in v22.2 and earlier. Support for this privilege model will be removed in a future release of CockroachDB:

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/hasura-getting-started.md:14
Hasura GraphQL Engine v2.16 and later supports CockroachDB v22.2 and later.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/hasura-getting-started.md:24
- An existing [{{ site.data.products.dedicated }}](../cockroachcloud/quickstart-trial-cluster.html) cluster, running CockroachDB v22.2 or later.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/install-cockroachdb-linux.md:118

For CockroachDB v22.2.beta-5 and above, Docker images are multi-platform images that contains binaries for both Intel and ARM. CockroachDB on ARM systems is experimental and is not yet qualified for production use. Multi-platform images do not take up additional space on your Docker host.

Docker images for previous releases contain Intel binaries only. Intel binaries can run on ARM systems, but with a significant reduction in performance.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/install-cockroachdb-mac.md:19

For CockroachDB v22.2.0 on ARM Macs, spatial features are disabled due to an issue with macOS code signing for the GEOS libraries. Users needing spatial features on an ARM Mac may instead use Rosetta to run the Intel binary or use the Docker image distribution. This issue is expected to be resolved in an upcoming 22.2 patch release. See the GitHub tracking issue for more information.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/install-cockroachdb-mac.md:24
{% capture arch_note_homebrew %}

For CockroachDB v22.2.x and above, Homebrew installs binaries for your system architecture, either Intel or ARM (Apple Silicon).

For previous releases, Homebrew installs Intel binaries. Intel binaries can run on ARM systems, but with a significant reduction in performance.

{% endcapture %}

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/install-cockroachdb-mac.md:26
{% capture arch_note_binaries %}

For CockroachDB v22.2.x and above, download the binaries for your system architecture, either Intel or ARM (Apple Silicon).

For previous releases, download Intel binaries. Intel binaries can run on ARM systems, but with a significant reduction in performance.

{% endcapture %}

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/install-cockroachdb-mac.md:28
{% capture arch_note_docker %}

For CockroachDB v22.2.beta-5 and above, Docker images are multi-platform images that contains binaries for both Intel and ARM (Apple Silicon). CockroachDB on ARM systems is experimental and is not yet qualified for production use. Multi-platform images do not take up additional space on your Docker host.

Docker images for previous releases contain Intel binaries only. Intel binaries can run on ARM systems, but with a significant reduction in performance.

{% endcapture %}

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/install-cockroachdb-windows.md:63

Docker images for previous releases contain Intel binaries only. Intel binaries can run on ARM systems, but with a significant reduction in performance.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/known-limitations.md:59
The [cluster setting](cluster-settings.html) `kv.rangefeed.range_stuck_threshold` will automatically restart a rangefeed that appears to be stuck if it does not emit events for some time. Rangefeeds are used to stream per-range changefeed events. This setting was introduced in CockroachDB v22.1.7, disabled by default, but is enabled by default in v22.2.0, set to 1 minute.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/multiregion-overview.md:117
This behavior is an improvement over versions of CockroachDB prior to v22.2. In those versions, when the primary region failed, the [leaseholders](architecture/replication-layer.html#leases) would be transferred to another [database region](#database-regions) at random, which could have negative effects on performance.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/node-shutdown.md:521
build: CCL v22.2.0-alpha.1 @ 2022/08/30 23:02:58 (go1.19.1)

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/restore.md:34
Starting in v22.2, CockroachDB introduces a new restore privilege model that provides finer control over a user's privilege to restore backups.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/restore.md:36
There is continued support for the [legacy privilege model](#required-privileges-using-the-legacy-privilege-model) in v22.2, however it **will be removed** in a future release of CockroachDB. We recommend implementing the new privilege model that follows in this section for all restores.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/restore.md:55
The following details the existing privilege model that CockroachDB supports in v22.2 and earlier. Support for this privilege model will be removed in a future release of CockroachDB:

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/restoring-backups-across-versions.md:14
Since CockroachDB considers the cluster version when running a backup, this page refers to versions in a "v22.2.x" format. For example, both v22.2.8 and v22.2.14 are considered as v22.2 clusters for backup purposes.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/row-level-ttl.md:138
| `ttl_expiration_expression` | **Recommended in v22.2+**. SQL expression that defines the TTL expiration. Must evaluate to a [`TIMESTAMPTZ`](timestamp.html). This and/or [`ttl_expire_after`](#param-ttl-expire-after) are required to enable TTL. This parameter is useful when you want to set the TTL for individual rows in the table. For an example, see [Create a table with a `ttl_expiration_expression`](#create-a-table-with-a-ttl_expiration_expression). | N/A |

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:15
Starting in v22.2, CockroachDB introduces a new granular [system-level privilege model](#system-level-privileges) that provides finer control over a user's ability to work with the database. This new system-level privilege model is intended to replace the existing [role options model](#role-options) in a future release of CockroachDB. As such, any legacy role options that now have corresponding system-level privilege versions are **deprecated in CockroachDB v22.2**, though both are supported alongside each other in v22.2. We recommend familiarizing yourself with the new system-level privilege model, and implementing it where possible.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:22
[System-level Privileges](#system-level-privileges) |

Introduced in CockroachDB v22.2.
Supported in CockroachDB v22.2, alongside the existing role options.
Apply cluster-wide. A system-level privilege is granted at the cluster level, and is inherited via role membership, similar to how [object-level privileges](#privileges) are inherited.
Are granted with the [`GRANT`](../grant.html) statement using the `SYSTEM` parameter, and viewed with the [`SHOW SYSTEM GRANTS`](../show-system-grants.html) statement.
May be assigned with the [`GRANT OPTION`](../grant.html), which allows the assigned user or role to further grant that same system-level privilege to other users or roles.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:23
[Role Options](#role-options) |

[Specific role options](#system-level-privileges) which have had corresponding system-level privileges introduced in CockroachDB v22.2 are now **deprecated**.
Supported in CockroachDB v22.2, alongside the new system-level privileges.
Apply only to specific users, and are not inheritable via role membership.
Are granted with the [`GRANT`](../grant.html) statement, and viewed with the [`SHOW GRANTS`](../show-grants.html) statement.
May be assigned with the [`GRANT OPTION`](../grant.html), which allows the assigned user or role to further grant that same role option to other users or roles.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:147
The following table lists the new system-level privileges introduced with CockroachDB v22.2, and indicates which system-level privileges replace role options:

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:152
`EXTERNALCONNECTION` | No, new in v22.2

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:158
`VIEWCLUSTERMETADATA` | No, new in v22.2

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:159
`VIEWDEBUG` | No, new in v22.2

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:160
`BACKUP` | No, new in v22.2

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:161
`RESTORE` | No, new in v22.2

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:162
`EXTERNALIOIMPLICITACCESS` | No, new in v22.2

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/authorization.md:163
`CHANGEFEED` | No, new in v22.2

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/scram-authentication.md:33
If you use Looker or Google Data Studio with CockroachDB v22.2 or later, you will need to fall back to hashing user passwords with bcrypt following the steps in [Downgrade from SCRAM authentication](../error-handling-and-troubleshooting.html#downgrade-from-scram-authentication).

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/scram-authentication.md:82
In CockroachDB v22.2.x and above, passwords are encrypted using SCRAM-SHA-256 by default, and the `server.user_login.password_encryption` [cluster setting](/docs/{{ page.version.version }}/cluster-settings.html) defaults to `scram-sha-256`. In CockroachDB v22.1.x and below, the setting defaults to `bcrypt`. When this setting is set to `scram-sha-256`, passwords created with the following SQL statements will be managed and authenticated according to SCRAM-SHA-256.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/scram-authentication.md:90
In CockroachDB v22.2x and above, `user_login.password_encryption` defaults to `scram-sha-256`. In CockroachDB v22.1.x and below, the default is `bcrypt`. Automatic eventual migration of existing users and roles from cleartext passwords to SCRAM-SHA-256 authentication is also enabled by default in CockroachDB v22.x and above. Refer to [Migrate existing users/roles from cleartext passwords to SCRAM SHA-256 authentication](#migrate-existing-users-roles-from-cleartext-passwords-to-scram-sha-256-authentication).

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/scram-authentication.md:122
In CockroachDB v22.2.x and above, the `server.user_login.upgrade_bcrypt_stored_passwords_to_scram.enabled` [cluster setting](/docs/{{ page.version.version }}/cluster-settings.html) is enabled by default. Because `user_login.password_encryption` also defaults to `scram-sha-256`, this means that by default, any user who still uses cleartext passwords will be migrated to SCRAM-SHA-256 authentication. To prevent this automatic migration, set `server.user_login.upgrade_bcrypt_stored_passwords_to_scram.enabled` to `false` before upgrading to CockroachDB v22.2.x.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/scram-authentication.md:179
In CockroachDB v22.2.x and above, the `server.user_login.upgrade_bcrypt_stored_passwords_to_scram.enabled` cluster setting is enabled by default. Because `user_login.password_encryption` also defaults to `scram-sha-256`, this means that by default, any user who still uses cleartext passwords will be migrated to SCRAM-SHA-256 authentication. Refer to [Eventual migration](#eventual-migration).

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/scram-authentication.md:194
Enable SCRAM for new passwords. In CockroachDB v22.2.x and above, this cluster setting defaults to `scram-sha-256`. In CockroachDB v22.1.x and below, it defaults to `bcrypt`.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/security-reference/scram-authentication.md:203
Enable the CockroachDB cluster to accept pre-computed SCRAM-SHA-256 salted password hashes, rather than accepting a cleartext password and computing the hash itself. In CockroachDB v22.2.x and above, this cluster setting is enabled by default.

/Users/ml/go/src/github.com/cockroachdb/docs/v23.1/upgrade-cockroach-version.md:35
In CockroachDB v22.2.x and above, a cluster that is upgraded to an alpha binary of CockroachDB or a binary that was manually built from the `master` branch cannot subsequently be upgraded to a production release.
```

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Manually review content that still mentions v22.2 in 23.1 docs after bump-major-version script

Description

Contributor guide

Assessment

Get new issues in your inbox