Skip to content

Commit

Permalink
Edited release notes
Browse files Browse the repository at this point in the history
  • Loading branch information
@kathancox
kathancox committed Jan 6, 2025
1 parent 86a4805 commit dd72780
Show file tree
Hide file tree
Showing 2 changed files with 36 additions and 50 deletions.
7 changes: 7 additions & 0 deletions src/current/_data/releases.yml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7761,3 +7761,10 @@
docker_arm_limited_access: false
source: true
previous_release: v24.2.7
cloud_only: true
cloud_only_message_short: 'Available only for select CockroachDB Cloud clusters'
cloud_only_message: >
This version is currently available only for select
CockroachDB Cloud clusters. To request to upgrade
a CockroachDB self-hosted cluster to this version,
[contact support](https://support.cockroachlabs.com/hc/requests/new).
79 changes: 29 additions & 50 deletions src/current/_includes/releases/v24.2/v24.2.8.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,68 +6,55 @@ Release Date: January 9, 2025

<h3 id="v24-2-8-general-changes">General changes</h3>

- In order to improve the granularity of changefeed pipeline metrics, the changefeed metrics changefeed.admit_latency and changefeed.commit_latency have histogram buckets from 5ms to 60m (previously 500ms to 5m). The changefeed metrics changefeed.parallel_io_queue_nanos, changefeed.parallel_io_result_queue_nanos, changefeed.sink_batch_hist_nanos, changefeed.flush_hist_nanos, and changefeed.kafka_throttling_hist_nanos have histogram buckets from 5ms to 10m (previously 500ms to 5m). [#136603][#136603]
- Add support for multiple seed brokers in the new kafka sink. [#136748][#136748]
- Add a new metric (`distsender.rangefeed.catchup_ranges_waiting_client_side`) that counts how many rangefeeds are waiting on the client-side limiter to start performing catchup scans. [#136835][#136835]
- To improve the granularity of changefeed pipeline metrics, the changefeed metrics `changefeed.admit_latency` and `changefeed.commit_latency` have histogram buckets from `5ms` to `60m` (previously `500ms` to `5m`). The following changefeed metrics have histogram buckets from `5ms` to `10m` (previously `500ms` to `5m`):
- `changefeed.parallel_io_queue_nanos`
- `changefeed.parallel_io_result_queue_nanos`
- `changefeed.sink_batch_hist_nanos`
- `changefeed.flush_hist_nanos`
- `changefeed.kafka_throttling_hist_nanos` [#136603][#136603]
- Added support for multiple seed brokers in the new Kafka sink. [#136748][#136748]
- Added a new metric (`distsender.rangefeed.catchup_ranges_waiting_client_side`) that counts how many rangefeeds are waiting on the client-side limiter to start performing catchup scans. [#136835][#136835]

<h3 id="v24-2-8-{{-site.data.products.enterprise-}}-edition-changes">{{ site.data.products.enterprise }} edition changes</h3>

- Adds changefeed support for the mvcc_timestamp option with the avro format. If both options are specified, the avro schema includes an mvcc_timestamp metadata field and emits the row's mvcc timestamp with the row data. [#136016][#136016]
- Adds no-op AWS_USE_PATH_STYLE param for forwards compatibility with 24.3. [#137025][#137025]
- Added changefeed support for the `mvcc_timestamp` option with the `avro` format. If both options are specified, the Avro schema includes an `mvcc_timestamp` metadata field and emits the row's mvcc timestamp with the row data. [#136016][#136016]
- Added a no-op `AWS_USE_PATH_STYLE` parameter for forward compatibility with v24.3. [#137025][#137025]

<h3 id="v24-2-8-sql-language-changes">SQL language changes</h3>

- The `legacy_varchar_typing` session setting has been added, which reverts the changes of #133037 that cause the change in typing behavior described in #137837. Specifically, it makes type-checking and overload resolution ignore the newly added "unpreferred" overloads. This setting defaults to `on`. [#137920][#137920]
- Added the `legacy_varchar_typing` session setting, which reverts the changes of [#133037](https://github.com/cockroachdb/cockroach/pull/133037) that causes the change in typing behavior described in [#137837](https://github.com/cockroachdb/cockroach/pull/137837). Specifically, it makes type-checking and overload resolution ignore the newly added "unpreferred" overloads. This setting defaults to `on`. [#137920][#137920]

<h3 id="v24-2-8-operational-changes">Operational changes</h3>

- Removed the sql.auth.resolve_membership_single_scan.enabled cluster setting. This was added out of precaution in case it was necessary to revert back to the old behavior for looking up role memberships, but this escape hatch has never been needed in practice since this was added in v23.1. [#136161][#136161]
- Removed the `sql.auth.resolve_membership_single_scan.enabled` cluster setting. This was added out of precaution in case it was necessary to revert back to the old behavior for looking up role memberships, but this escape hatch has never been needed in practice since this was added in v23.1. [#136161][#136161]
- Telemetry delivery is now considered successful even in cases where we experience a network timeout. This will prevent throttling in cases outside an operator's control. [#136479][#136479]
- When a schema change job is completed, rolls back, or encounteres a failure, the time taken since the job began is now logged in a structured log in the SQL_SCHEMA log channel. [#136928][#136928]
- Adds a new configurable parameter kv.transaction.max_intents_and_locks which will prevent transactions from creating too many intents. [#137700][#137700]
- Add metric txn.count_limit_rejected. [#137700][#137700]
- Add metric txn.count_limit_on_response. [#137700][#137700]
- When a schema change job is completed, rolls back, or encounters a failure, the time taken since the job began is now logged in a structured log in the `SQL_SCHEMA` log channel. [#136928][#136928]
- Added a new configurable parameter `kv.transaction.max_intents_and_locks` that will prevent transactions from creating too many intents. [#137700][#137700]
- Added the metric `txn.count_limit_rejected`, which tracks the KV transactions that have been aborted because they exceeded the max number of writes and locking reads allowed. [#137700][#137700]
- Added the metric `txn.count_limit_on_response`, which tracks the number of KV transactions that have exceeded the count limit on a response. [#137700][#137700]

<h3 id="v24-2-8-bug-fixes">Bug fixes</h3>

- ALTER COLUMN SET NOT NULL was not enforced consistently when the table created in the same txn. [#136365][#136365]
- Create relation / type could leave dangling namespace entries if the schema was concurrently being dropped. [#136379][#136379]
- `ALTER COLUMN SET NOT NULL` was not enforced consistently when the table was created in the same transaction. [#136365][#136365]
- Fixed a bug where `CREATE RELATION / TYPE` could leave dangling namespace entries if the schema was concurrently being dropped. [#136379][#136379]
- The `idle_in_session_timeout` setting now excludes the time spent waiting for schema changer jobs to complete, preventing unintended session termination during schema change operations. [#136502][#136502]
- Fix a bug which causes the optimizer to use stale table statistics after altering an enum type used in the table. [#136759][#136759]
- Table statistics collection in CockroachDB could previously run into `no bytes in account to release` errors in some edge cases (when the SQL memory budget, configured via `--max-sql-memory` flag, was close to being exhausted). The bug has been present since 21.2 and is now fixed. [#136165][#136165]
- Fixed a bug that causes the optimizer to use stale table statistics after altering an `ENUM` type used in the table. [#136759][#136759]
- Table statistics collection in CockroachDB could previously run into `no bytes in account to release` errors in some edge cases (when the SQL memory budget, configured via `--max-sql-memory` flag, was close to being exhausted). The bug has been present since v21.2 and is now fixed. [#136165][#136165]
- CockroachDB now better respects `statement_timeout` limit on queries involving the top K sort and merge join operations. [#136652][#136652]
- Fixed an issue where license enforcement was not consistently disabled for single-node clusters started with start-single-node, ensuring proper behavior on cluster restarts. [#137011][#137011]
- Fix a bug that caused queries against tables with user-defined types to sometimes fail with errors after restoring those tables. [#137354][#137354]
- Fixed bug that causes an incorrect filesystem to be logged as part of the store information. [#137113][#137113]
- Fix a bug which causes the optimizer to use stale table statistics after altering an enum type used in the table. [#137592][#137592]
- Fixed a bug existing since v24.1 that would cause a set-returning UDF with OUT parameters to return a single row. [#137377][#137377]
- Fixed a bug that could cause an internal error if a table with an implicit (rowid) primary key was locked from within a subquery, like this: ``` SELECT * FROM (SELECT * FROM foo WHERE x = 2) FOR UPDATE; ``` The error could occur either under read-committed isolation, or with `optimizer_use_lock_op_for_serializable` enabled. [#137129][#137129]
- Fixed an issue where adding an existing column with the IF NOT EXISTS option could exit too early, skipping necessary handling of the AST. This could lead to statement failure of the ALTER. [#137676][#137676]
- Fixed a bug related to displaying the names of composite types in the SHOW CREATE TABLES command. The names are now shown as two-part names, which disambiguates the output and makes it more portable to other databases. [#137768][#137768]
- An issue where a schema change could incorrectly cause a changefeed to fail with an assertion error like `received boundary timestamp ... of type ... before reaching existing boundary of type ...` has now been fixed. [#137705][#137705]
- Internal scans are now exempt from the sql.defaults.disallow_full_table_scans.enabled setting, allowing index creation even when the cluster setting is active. [#137724][#137724]
- Fixed an issue where license enforcement was not consistently disabled for single-node clusters started with `cockroach start-single-node`. The fix ensures proper behavior on cluster restarts. [#137011][#137011]
- Fixed a bug that caused queries against tables with user-defined types to sometimes fail with errors after restoring those tables. [#137354][#137354]
- Fixed a bug that causes an incorrect filesystem to be logged as part of the store information. [#137113][#137113]
- Fixed a bug that has existed since v24.1 that would cause a set-returning UDF with `OUT` parameters to return a single row. [#137377][#137377]
- Fixed a bug that could cause an internal error if a table with an implicit (`rowid`) primary key was locked from within a subquery, like: `SELECT * FROM (SELECT * FROM foo WHERE x = 2) FOR UPDATE;`. The error could occur either under read-committed isolation, or with `optimizer_use_lock_op_for_serializable` enabled. [#137129][#137129]
- Fixed an issue where adding an existing column with the `IF NOT EXISTS` option could exit too early, skipping necessary handling of the abstract syntax tree (AST). This could lead to failure of the `ALTER` statement. [#137676][#137676]
- Fixed a bug related to displaying the names of composite types in the `SHOW CREATE TABLES` command. The names are now shown as two-part names, which disambiguates the output and makes it more portable to other databases. [#137768][#137768]
- Fixed an issue where a schema change could incorrectly cause a changefeed to fail with an assertion error like `received boundary timestamp ... of type ... before reaching existing boundary of type ...`. [#137705][#137705]
- Internal scans are now exempt from the `sql.defaults.disallow_full_table_scans.enabled` setting, allowing index creation even when the cluster setting is active. [#137724][#137724]

<h3 id="v24-2-8-performance-improvements">Performance improvements</h3>

- Improved the internal caching logic for role membership information. This reduces the latency impact of commands such as `DROP ROLE`, `CREATE ROLE`, and `GRANT role TO user`, which cause the role membership cache to be invalidated. [#136161][#136161]

<h3 id="v24-2-8-miscellaneous">Miscellaneous</h3>

<h4 id="v24-2-8-changes-without-release-note-annotation">Changes without release note annotation</h4>

- [#137461][#137461] [554746b85][554746b85] release-24.2: docgen: remove unused BEGIN diagram (#137461)
- [#137116][#137116] [f6d3766dc][f6d3766dc] release-24.2: docgen: update BEGIN and SET TRANSACTION diagrams (#137116)
- [#136681][#136681] [b6cb00b43][b6cb00b43] release-24.2: TEAMS: ping kv-triage for unittest failures
- [#136681][#136681] [c81aee156][c81aee156] release-24.2: TEAMS: ping kv-triage for unittest failures
- [#136681][#136681] [a14d96a29][a14d96a29] release-24.2: TEAMS: ping kv-triage for unittest failures
- [#136681][#136681] [381fe2527][381fe2527] release-24.2: TEAMS: ping kv-triage for unittest failures
- [#136471][#136471] [94d8e00bb][94d8e00bb] release-24.2: roachprod: add sufficient tenant ids when creating v22.2 client certs

<h3 id="v24-2-8-doc-updates">Doc updates</h3>

{% comment %}Docs team: Please add these manually.{% endcomment %}



[#136016]: https://github.com/cockroachdb/cockroach/pull/136016
[#136161]: https://github.com/cockroachdb/cockroach/pull/136161
Expand All @@ -92,17 +79,9 @@ Release Date: January 9, 2025
[#137354]: https://github.com/cockroachdb/cockroach/pull/137354
[#137377]: https://github.com/cockroachdb/cockroach/pull/137377
[#137461]: https://github.com/cockroachdb/cockroach/pull/137461
[#137592]: https://github.com/cockroachdb/cockroach/pull/137592
[#137676]: https://github.com/cockroachdb/cockroach/pull/137676
[#137700]: https://github.com/cockroachdb/cockroach/pull/137700
[#137705]: https://github.com/cockroachdb/cockroach/pull/137705
[#137724]: https://github.com/cockroachdb/cockroach/pull/137724
[#137768]: https://github.com/cockroachdb/cockroach/pull/137768
[#137920]: https://github.com/cockroachdb/cockroach/pull/137920
[381fe2527]: https://github.com/cockroachdb/cockroach/commit/381fe2527
[554746b85]: https://github.com/cockroachdb/cockroach/commit/554746b85
[94d8e00bb]: https://github.com/cockroachdb/cockroach/commit/94d8e00bb
[a14d96a29]: https://github.com/cockroachdb/cockroach/commit/a14d96a29
[b6cb00b43]: https://github.com/cockroachdb/cockroach/commit/b6cb00b43
[c81aee156]: https://github.com/cockroachdb/cockroach/commit/c81aee156
[f6d3766dc]: https://github.com/cockroachdb/cockroach/commit/f6d3766dc

0 comments on commit dd72780

Please sign in to comment.