Skip to content

Commit

Permalink
Partial edit
Browse files Browse the repository at this point in the history
  • Loading branch information
mikeCRL committed Jan 24, 2025
1 parent 8130214 commit 9eb3ced
Showing 1 changed file with 9 additions and 4 deletions.
13 changes: 9 additions & 4 deletions src/current/_includes/releases/v25.1/v25.1.0-beta.2.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,16 +6,21 @@ Release Date: January 27, 2025

<h3 id="v25-1-0-beta-2-sql-language-changes">SQL language changes</h3>

- SHOW JOBS is now based on a new mechanism for storing information about the progress and status of running jobs. Epic: none. [#139230][#139230]
- SHOW TENANT WITH REPLICATION STATUS will now display the `ingestion_job_id` column after the `name` column. [#139275][#139275]
- `SHOW JOBS` is now based on a new mechanism for storing information about the progress and status of running jobs. [#139230][#139230]
- `SHOW TENANT WITH REPLICATION STATUS` now displays the `ingestion_job_id` column after the `name` column. [#139275][#139275]

<h3 id="v25-1-0-beta-2-operational-changes">Operational changes</h3>

- Customers must pass URIs as external connections to create LDR statments. [#139506][#139506]
- Customers must pass URIs as [external connections]({% link {{ page.version.version }}/create-external-connection.md %}) when [setting up Logical Data Replication (LDR)]({% link {{ page.version.version }}/set-up-logical-data-replication.md %}). [#139506][#139506]

<h3 id="v25-1-0-beta-2-db-console-changes">DB Console changes</h3>

- The /_admin/v1/settings API (and therfore cluster settings console page) now returns cluster settings using the same redaction logic as querying `SHOW CLUSTER SETTINGS` and `crdb_internal.cluster_settings`. This means that only settings flagged as "sensitive" will be redacted, all other settings will be visible. The same authorization is required for this endpoint, meaning the user must be an admin or have MODIFYCLUSTERSETTINGS or VIEWCLUSTERSETTINGS roles to hit this API. The exception is that if the user has VIEWACTIVITY or VIEWACTIVITYREDACTED, they will see console only settings. [#139277][#139277]
- The DB Console Cluster Settings page and `/_admin/v1/settings` API now use the same authorization and redaction logic as `SHOW CLUSTER SETTINGS` and `crdb_internal.cluster_settings`:
- Users need `ADMIN`, `MODIFYCLUSTERSETTINGS`, or `VIEWCLUSTERSETTINGS` privileges to view settings.
- If you have [enabled redaction of sensitive settings]({% link {{ page.version.version }}/cluster-settings.md %}#setting-server-redact-sensitive-settings-enabled), only users with `ADMIN` or `MODIFYCLUSTERSETTINGS` permissions can view values of settings CockroachDB classifies as `sensitive`.
- Users with `VIEWACTIVITY` or `VIEWACTIVITYREDACTED` roles can only access settings pertaining to the DB Console.

This change provides consistent behavior across all methods of accessing cluster settings. [#139277][#139277]
- The overload dashboard on DB Console now shows only the v2 replication admission control metrics, where previously it displayed both v1 and v2 metrics. Additionally, the aggregate size of queued replication entries is now shown. [#139566][#139566]

<h3 id="v25-1-0-beta-2-bug-fixes">Bug fixes</h3>
Expand Down

0 comments on commit 9eb3ced

Please sign in to comment.