From 568a1d6c49d539c1e0c5e41197e6635cb5a25cfc Mon Sep 17 00:00:00 2001 From: Lauren Hirata Singh Date: Mon, 15 May 2023 16:04:27 -0400 Subject: [PATCH 1/4] Quick follow on 23.1.0 release notes --- _includes/releases/v23.1/v23.1.0.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/_includes/releases/v23.1/v23.1.0.md b/_includes/releases/v23.1/v23.1.0.md index 84b3f5aba3e..4b35a8d91ce 100644 --- a/_includes/releases/v23.1/v23.1.0.md +++ b/_includes/releases/v23.1/v23.1.0.md @@ -231,6 +231,10 @@ Asyncpg is commonly used with ORM libraries such as SQLAlchemy to provide a simp
Change data capture (Changefeeds)
+{{site.data.alerts.callout_info}} +The following are [enterprise-only](../v23.1/enterprise-licensing.html) features. [Request a 30-day trial license](https://www.cockroachlabs.com/get-cockroachdb/enterprise/) to try them out. +{{site.data.alerts.end}} + @@ -260,7 +264,7 @@ Asyncpg is commonly used with ORM libraries such as SQLAlchemy to provide a simp - @@ -268,7 +272,7 @@ With the move from Preview to GA, this feature brings many new capabilities, suc - @@ -354,7 +358,7 @@ If the node executing the backup does not have a specific range to be backed up, - From 89a396af4ab11cc6b36f41f38a7265cfe6cce2ae Mon Sep 17 00:00:00 2001 From: Lauren Hirata Singh Date: Mon, 15 May 2023 16:22:14 -0400 Subject: [PATCH 2/4] Quick follow on 23.1.0 release notes --- _includes/releases/v23.1/v23.1.0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_includes/releases/v23.1/v23.1.0.md b/_includes/releases/v23.1/v23.1.0.md index 4b35a8d91ce..643d872e91c 100644 --- a/_includes/releases/v23.1/v23.1.0.md +++ b/_includes/releases/v23.1/v23.1.0.md @@ -358,13 +358,13 @@ If the node executing the backup does not have a specific range to be backed up, - - From 7827a95816959524208b9337388435751152abac Mon Sep 17 00:00:00 2001 From: Nick Vigilante Date: Mon, 15 May 2023 16:33:48 -0400 Subject: [PATCH 3/4] Updates to version switcher If `dev` is listed first within `_config_cockroachdb.yml` > versions, its version tag will be shown as "Dev", even if it's the same as "Stable". This commit fixes that. --- _includes/version-switcher.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_includes/version-switcher.html b/_includes/version-switcher.html index a1e8ccf3ca3..ff400a73c50 100644 --- a/_includes/version-switcher.html +++ b/_includes/version-switcher.html @@ -17,7 +17,7 @@ class="version--mobile version--page-dne" {% endif %}> {{ v.version.name }} - {% if v.version.tag %}{% unless v.version.tag == "cloud" %}({{ v.version.tag | capitalize }}){% endunless %}{% endif %} + {% unless v.version.tag == "cloud" or v.version.tag == nil %}({% if v.version.version == site.versions["stable"] %}Stable{% elsif v.version.version == site.versions["dev"] %}Dev{% endif %}){% endunless %} {% unless v.url %} This page does not exist in {{ v.version.version }} @@ -33,7 +33,7 @@ data-tooltip data-placement="left" data-container="body" title="This page does not exist in {{ v.version.version }}." {% endif %}> {{ v.version.name }} - {% if v.version.tag %}({{ v.version.tag | capitalize }}){% endif %} + {% if v.version.tag %}({% if v.version.version == site.versions["stable"] %}Stable{% elsif v.version.version == site.versions["dev"] %}Dev{% endif %})e{% endif %} {% endfor %} From 1792d7f3965a25b264a4fcd3450355331e9a401c Mon Sep 17 00:00:00 2001 From: Nick Vigilante Date: Mon, 15 May 2023 17:05:47 -0400 Subject: [PATCH 4/4] fix typo --- _includes/version-switcher.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_includes/version-switcher.html b/_includes/version-switcher.html index ff400a73c50..ad28291bda5 100644 --- a/_includes/version-switcher.html +++ b/_includes/version-switcher.html @@ -33,7 +33,7 @@ data-tooltip data-placement="left" data-container="body" title="This page does not exist in {{ v.version.version }}." {% endif %}> {{ v.version.name }} - {% if v.version.tag %}({% if v.version.version == site.versions["stable"] %}Stable{% elsif v.version.version == site.versions["dev"] %}Dev{% endif %})e{% endif %} + {% if v.version.tag %}({% if v.version.version == site.versions["stable"] %}Stable{% elsif v.version.version == site.versions["dev"] %}Dev{% endif %}){% endif %} {% endfor %}

Use External Connections (GA) to remove a data exfiltration vector

Use external connections to specify and interact with resources that are external from CockroachDB. With CREATE EXTERNAL CONNECTION, you define a name for an external connection while passing the provider URI and query parameters. BACKUP, RESTORE, IMPORT, EXPORT, and CREATE CHANGEFEED queries can interact with the defined external connection instead of a required, provider-specific URI. As a result, you can decouple the management and permissions of the external resource from the operation in which you're using them. +

Use external connections to specify and interact with resources that are external from CockroachDB. With CREATE EXTERNAL CONNECTION, you define a name for an external connection while passing the provider URI and query parameters. BACKUP, RESTORE, IMPORT, EXPORT, and CREATE CHANGEFEED queries can interact with the defined external connection instead of a required, provider-specific URI. As a result, you can decouple the management and permissions of the external resource from the operation in which you're using them.

With the move from Preview to GA, this feature brings many new capabilities, such as fine-grained permission and support for schema registries, webhook and GC PubSub sinks, and the SHOW command.

Changefeed locality

CREATE CHANGEFEED now accepts a 'WITH execution_locality' option to restrict execution of the changefeed process to nodes within the specified locality filter. +

CREATE CHANGEFEED now accepts a WITH execution_locality option to restrict execution of the changefeed process to nodes within the specified locality filter.

Enhanced Intelligent Insights experience includes transaction-level insights and metrics

We have expanded the [Insights](../v23.1/ui-insights-page.html#transaction-executions-view) section of the Console, offering improved discoverability and data for tuning and optimizing your workload. Contention insights reveal the waiting statement for cases where blocking conflicts occur. Transaction-level insights help you identify impacted areas of your application and prioritize your investigations, enabling you to drill down to individual statements with suboptimal plans. +

We have expanded the Insights section of the Console, offering improved discoverability and data for tuning and optimizing your workload. Contention insights reveal the waiting statement for cases where blocking conflicts occur. Transaction-level insights help you identify impacted areas of your application and prioritize your investigations, enabling you to drill down to individual statements with suboptimal plans.

Enhanced Intelligent Insights experience includes transaction-level insights and metrics

We have expanded the Insights section of the Console, offering improved discoverability and data for tuning and optimizing your workload. Contention insights reveal the waiting statement for cases where blocking conflicts occur. Transaction-level insights help you identify impacted areas of your application and prioritize your investigations, enabling you to drill down to individual statements with suboptimal plans. +

We have expanded the Insights section of the Console, offering improved discoverability and data for tuning and optimizing your workload. Contention insights reveal the waiting statement for cases where blocking conflicts occur. Transaction-level insights help you identify impacted areas of your application and prioritize your investigations, enabling you to drill down to individual statements with additional insights such as suboptimal plans.

Enhanced statement metrics

Easily correlate high-level cluster metrics (e.g., CPU, latency, etc.) with per-statement CPU utilization, latency metrics (P50, P90, P99, min, max), idle/client time, and MVCC garbage statistics. +

Easily correlate high-level cluster metrics (e.g., CPU, latency, etc.) with per-statement CPU utilization, latency metrics (P50, P90, P99, min, max), idle/client wait time, and MVCC garbage statistics.