-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[release-19.0] Release of v19.0.0
#15359
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
1571f4d
Unfreeze branch release-19.0
systay f32d2e6
Addition of release notes
systay 7bef027
Update codebase for the v19.0.0 release
systay f1e6602
Re-generate the release notes
frouioui aa3d641
Rename PR 15377
frouioui af547d6
Regen the release notes
frouioui 26449b7
Merge remote-tracking branch 'upstream/release-19.0' into release-19.…
systay bc4d9d5
regen release notes
systay cb83cea
Merge remote-tracking branch 'upstream/release-19.0' into release-19.…
systay 32bbed9
Update release notes
systay File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,4 +11,4 @@ jobs: | |
steps: | ||
- name: Fail if Code Freeze is enabled | ||
run: | | ||
exit 1 | ||
exit 0 |
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,29 +4,29 @@ | |
### Table of Contents | ||
|
||
- **[Major Changes](#major-changes)** | ||
- **[Dropping Support for MySQL 5.7](#drop-support-mysql57)** | ||
- **[Deprecations and Deletions](#deprecations-and-deletions)** | ||
- [VTTablet Flags](#vttablet-flags) | ||
- [Docker Image vitess/lite](#deprecation-vitess-lite-mysqld) | ||
- [Explain Statement Format](#explain-stmt-format) | ||
- **[Breaking Changes](#breaking-changes)** | ||
- [ExecuteFetchAsDBA rejects multi-statement SQL](#execute-fetch-as-dba-reject-multi) | ||
- **[New Stats](#new-stats)** | ||
- [Stream Consolidations](#stream-consolidations) | ||
- [Build Version in `/debug/vars`](#build-version-in-debug-vars) | ||
- **[Planned Reparent Shard](#planned-reparent-shard)** | ||
- [`--tolerable-replication-lag` Sub-flag](#tolerable-repl-lag) | ||
- **[Query Compatibility](#query-compatibility)** | ||
- [Multi Table Delete Support](#multi-table-delete) | ||
- [`SHOW VSCHEMA KEYSPACES` Query](#show-vschema-keyspaces) | ||
- [`FOREIGN_KEY_CHECKS` is now a Vitess Aware Variable](#fk-checks-vitess-aware) | ||
- [Explain Statement](#explain-statement) | ||
- [Partial Multi-shard Commit Warnings](#partial-multi-shard-commit-warnings) | ||
- [New Lock Syntax](#lock-syntax) | ||
- [Support for AVG()](#avg-support) | ||
- [Support for non-recursive CTEs](#cte-support) | ||
- **[Vttestserver](#vttestserver)** | ||
- [`--vtcombo-bind-host` flag](#vtcombo-bind-host) | ||
- **[Dropping Support for MySQL 5.7](#drop-support-mysql57)** | ||
- **[Deprecations and Deletions](#deprecations-and-deletions)** | ||
- [VTTablet Flags](#vttablet-flags) | ||
- [Docker Image vitess/lite](#deprecation-vitess-lite-mysqld) | ||
- [Explain Statement Format](#explain-stmt-format) | ||
- **[Breaking Changes](#breaking-changes)** | ||
- [ExecuteFetchAsDBA rejects multi-statement SQL](#execute-fetch-as-dba-reject-multi) | ||
- **[New Stats](#new-stats)** | ||
- [Stream Consolidations](#stream-consolidations) | ||
- [Build Version in `/debug/vars`](#build-version-in-debug-vars) | ||
- **[Planned Reparent Shard](#planned-reparent-shard)** | ||
- [`--tolerable-replication-lag` Sub-flag](#tolerable-repl-lag) | ||
- **[Query Compatibility](#query-compatibility)** | ||
- [Multi Table Delete Support](#multi-table-delete) | ||
- [`SHOW VSCHEMA KEYSPACES` Query](#show-vschema-keyspaces) | ||
- [`FOREIGN_KEY_CHECKS` is now a Vitess Aware Variable](#fk-checks-vitess-aware) | ||
- [Explain Statement](#explain-statement) | ||
- [Partial Multi-shard Commit Warnings](#partial-multi-shard-commit-warnings) | ||
- [New Lock Syntax](#lock-syntax) | ||
- [Support for AVG()](#avg-support) | ||
- [Support for non-recursive CTEs](#cte-support) | ||
- **[Vttestserver](#vttestserver)** | ||
- [`--vtcombo-bind-host` flag](#vtcombo-bind-host) | ||
- **[Minor Changes](#minor-changes)** | ||
- **[Apply VSchema](#apply-vschema)** | ||
- [`--strict` sub-flag and `strict` gRPC field](#strict-flag-and-field) | ||
|
@@ -48,7 +48,7 @@ Vitess will however, continue to support importing from MySQL 5.7 into Vitess ev | |
#### <a id="vttablet-flags"/>VTTablet Flags | ||
|
||
- The following flags — which were deprecated in Vitess 7.0 — have been removed: | ||
`--vreplication_healthcheck_topology_refresh`, `--vreplication_healthcheck_retry_delay`, and `--vreplication_healthcheck_timeout`. | ||
`--vreplication_healthcheck_topology_refresh`, `--vreplication_healthcheck_retry_delay`, and `--vreplication_healthcheck_timeout`. | ||
- The `--vreplication_tablet_type` flag is now deprecated and ignored. | ||
|
||
#### <a id="deprecation-vitess-lite-mysqld"/>Docker Image vitess/lite | ||
|
@@ -158,7 +158,7 @@ mysql> show vschema keyspaces; | |
|
||
#### <a id="fk-checks-vitess-aware"/>`FOREIGN_KEY_CHECKS` is now a Vitess Aware Variable | ||
|
||
When VTGate receives a query to change the `FOREIGN_KEY_CHECKS` value for a session, instead of sending the value down to MySQL, VTGate now keeps track of the value and changes the queries by adding `SET_VAR(FOREIGN_KEY_CHECKS=On/Off)` style query optimizer hints wherever required. | ||
When VTGate receives a query to change the `FOREIGN_KEY_CHECKS` value for a session, instead of sending the value down to MySQL, VTGate now keeps track of the value and changes the queries by adding `SET_VAR(FOREIGN_KEY_CHECKS=On/Off)` style query optimizer hints wherever required. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Trailing space added in error? |
||
|
||
#### <a id="explain-statement"/>Explain Statement | ||
|
||
|
@@ -203,7 +203,7 @@ Vtgate can now evaluate `AVG` on sharded keyspaces, by using a combination of `S | |
|
||
### <a id="cte-support"/>Support for non-recursive CTEs | ||
|
||
Common table expressions that are not recursive can now be used. | ||
Common table expressions that are not recursive can now be used. | ||
|
||
```sql | ||
with userCount as ( | ||
|
@@ -220,10 +220,10 @@ from ref join userCount on ref.user_id = userCount.id | |
|
||
A new sub-flag `--strict` has been added to the command `ApplyVSchema` `vtctl` command that produces an error if unknown params are found in any Vindexes. An equivalent `strict` field has been added to the `ApplyVSchema` gRPC `vtctld` command. | ||
|
||
|
||
------------ | ||
The entire changelog for this release can be found [here](https://github.com/vitessio/vitess/blob/main/changelog/19.0/19.0.0/changelog.md). | ||
|
||
The release includes 412 merged Pull Requests. | ||
The release includes 461 merged Pull Requests. | ||
|
||
Thanks to all our contributors: @ChaitanyaD48, @EshaanAgg, @FirePing32, @GuptaManan100, @Its-Maniaco, @Maniktherana, @Manni-99, @MrFabio, @VaibhavMalik4187, @ajm188, @aparajon, @app/dependabot, @app/github-actions, @app/vitess-bot, @aquarapid, @arthurschreiber, @austenLacy, @beingnoble03, @brendar, @davidpiegza, @dbussink, @deepthi, @derekperkins, @ejortegau, @frouioui, @gerayking, @glokta1, @harshit-gangal, @iheanyi, @jwangace, @lixin963, @mattlord, @mattrobenolt, @maxenglander, @mcrauwel, @mdlayher, @olyazavr, @pbibra, @pnacht, @rajivharlalka, @ravicodelabs, @rbranson, @rohit-nayak-ps, @samanthadrago, @shlomi-noach, @skullface, @systay, @testwill, @tycol7, @vmg, @wangweicugw, @williammartin, @wlx5575 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indentation level changed in error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I am seeing it doesn't affect the format on GitHub.