Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOC-10090][DOC-10093] v24.1.0 deprecations, backward-incompatible changes, licensing updates #18530

Merged
merged 1 commit into from May 17, 2024

Conversation

mdlinville
Copy link
Contributor

@mdlinville mdlinville commented May 9, 2024

[DOC-10090] v24.1.0 deprecations and backward-incompatible changes
[DOC-10093] v24.1.0 licensing updates

  • Also fix a display bug in v23.1.0 release notes

Relates to [DOC-10061]

Preview: releases/v24.1.md

Copy link

github-actions bot commented May 9, 2024

Files changed:

Copy link

netlify bot commented May 9, 2024

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit 7615fd9
🔍 Latest deploy log https://app.netlify.com/sites/cockroachdb-interactivetutorials-docs/deploys/6647d70504e6e400088ee0cc

Copy link

netlify bot commented May 9, 2024

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit 7615fd9
🔍 Latest deploy log https://app.netlify.com/sites/cockroachdb-api-docs/deploys/6647d705daa0020008db8a16

Copy link

netlify bot commented May 9, 2024

Netlify Preview

Name Link
🔨 Latest commit 7615fd9
🔍 Latest deploy log https://app.netlify.com/sites/cockroachdb-docs/deploys/6647d705864e1a00080766f2
😎 Deploy Preview https://deploy-preview-18530--cockroachdb-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@taroface
Copy link
Contributor

taroface commented May 9, 2024

Here's my suggested addition:

The `sql.txn.read_committed_isolation.enabled` [cluster setting]({% link {{ page.version.version }}/cluster-setting.md %}) is now `true` by default. [`READ COMMITTED`]({% link {{ page.version.version }}/read-committed.md %}) transactions are no longer automatically upgraded to [`SERIALIZABLE`]({% link {{ page.version.version }}/demo-serializable.md %}), and will run as `READ COMMITTED`. As a result, upgrading CockroachDB may affect your application behavior. To see whether any transactions are being upgraded from weaker isolation levels to `SERIALIZABLE` on v23.2, check the [**Upgrades of SQL Transaction Isolation Level**]({% link {{ page.version.version }}/ui-sql-dashboard.md %}#upgrades-of-sql-transaction-isolation-level) graph in the DB Console. You may need to adjust those transactions before upgrading to v24.1.

If this needs to be associated with a PR, I think this should be the one: cockroachdb/cockroach#118479

See: cockroachdb/cockroach#118497 and this comment for context

@mdlinville
Copy link
Contributor Author

Here's my suggested addition:

The `sql.txn.read_committed_isolation.enabled` [cluster setting]({% link {{ page.version.version }}/cluster-setting.md %}) is now `true` by default. [`READ COMMITTED`]({% link {{ page.version.version }}/read-committed.md %}) transactions are no longer automatically upgraded to [`SERIALIZABLE`]({% link {{ page.version.version }}/demo-serializable.md %}), and will run as `READ COMMITTED`. As a result, upgrading CockroachDB may affect your application behavior. To see whether any transactions are being upgraded from weaker isolation levels to `SERIALIZABLE` on v23.2, check the [**Upgrades of SQL Transaction Isolation Level**]({% link {{ page.version.version }}/ui-sql-dashboard.md %}#upgrades-of-sql-transaction-isolation-level) graph in the DB Console. You may need to adjust those transactions before upgrading to v24.1.

If this needs to be associated with a PR, I think this should be the one: cockroachdb/cockroach#118479

See: cockroachdb/cockroach#118497 and this comment for context

Thanks, PTAL, I took your wording and gave it a few nitpicky tweaks.

@taroface taroface self-requested a review May 10, 2024 14:31
Copy link
Contributor

@taroface taroface left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The READ COMMITTED item LGTM!

@@ -241,7 +241,8 @@ In CockroachDB Self-Hosted, all available features are free to use unless their

Before [upgrading to CockroachDB v24.1]({% link v24.1/upgrade-cockroach-version.md %}), be sure to review the following backward-incompatible changes, as well as [key cluster setting changes](#v24-1-0-cluster-settings), and adjust your deployment as necessary.

- TBD
- [`AS OF SYSTEM TIME`]({% link v23.2/as-of-system-time.md %}) queries can no longer use a timestamp followed by a question mark to signify a future-time value. This was an undocumented syntax. [#116830](https://github.com/cockroachdb/cockroach/pull/116830)
- The `sql.txn.read_committed_isolation.enabled` [cluster setting]({% link v24.1/cluster-settings.md %}) is now `true` by default. As a result, [`READ COMMITTED`]({% link v24.1/read-committed.md %}) transactions are **not** automatically upgraded to [`SERIALIZABLE`]({% link v24.1/demo-serializable.md %}), and will run as `READ COMMITTED` by default. On v23.2, refer to the [**Upgrades of SQL Transaction Isolation Level**]({% link v24.1/ui-sql-dashboard.md %}#upgrades-of-sql-transaction-isolation-level) graph in the DB Console to check whether any transaction is being upgraded from a weaker isolation level to `SERIALIZABLE`, and could therefore run differently on v24.1. [#118479](https://github.com/cockroachdb/cockroach/pull/118479)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of the info looks correct to me. Just one more higher level question -- should this also mention that READ COMMITTED is enterprise only?

I.e., if you don't have an enterprise license, then even if the setting is on, the auto-upgrade to SERIALIZABLE will still happen. (Maybe this is something better left for the detailed docs, and I also don't want to derail this PR too much. I'm fine with whatever you decide, just mentioning it in case.)

Copy link
Contributor

@taroface taroface May 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK that's an important point -- I think this needs to be a separate backward-incompatible note, placed above this one about the txn upgrades.

cc @mdlinville (this just keeps the wording of the release note):

- The `READ COMMITTED` isolation level now requires the cluster to have a valid enterprise license. [#120154](https://github.com/cockroachdb/cockroach/pull/120154)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. PTAL because I added a little more detail to the end of your draft, and also added it to a new Enterprise Features section directly above the Backward-Incompatible Changes section.

@mdlinville mdlinville changed the title [DOC-10090] v24.1.0 deprecations and backward-incompatible changes [DOC-10090][DOC-10093] v24.1.0 deprecations, backward-incompatible changes, licensing updates May 13, 2024
Copy link
Contributor

@rafiss rafiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

Copy link
Contributor

@taroface taroface left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 correction and 1 clarification - let me know if it makes sense.

src/current/_includes/releases/v24.1/v24.1.0.md Outdated Show resolved Hide resolved
src/current/_includes/releases/v24.1/v24.1.0.md Outdated Show resolved Hide resolved
Copy link
Contributor

@taroface taroface left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, one formatting nit

src/current/_includes/releases/v24.1/v24.1.0.md Outdated Show resolved Hide resolved
src/current/_includes/releases/v24.1/v24.1.0.md Outdated Show resolved Hide resolved
…anges, license changes

- Also fix a display bug in v23.1.0 release notes
- Also update license conversion timelines for 23.2 and 24.1
@mdlinville mdlinville enabled auto-merge (squash) May 17, 2024 22:16
@mdlinville mdlinville merged commit aaaf92d into main May 17, 2024
6 of 7 checks passed
@mdlinville mdlinville deleted the DOC-10090 branch May 17, 2024 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants