-
Notifications
You must be signed in to change notification settings - Fork 234
Vitess 8 announcement blog #575
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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 hidden or 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 |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| --- | ||
| author: 'Alkin Tezuysal' | ||
| date: 2020-10-27 | ||
| slug: '2020-10-27-announcing-vitess-8' | ||
| tags: ['release'] | ||
| title: 'Announcing Vitess 8' | ||
| --- | ||
| On behalf of the Vitess maintainers’ team, I am pleased to announce the general availability of [Vitess 8](https://github.com/vitessio/vitess/releases/tag/v8.0.0). | ||
|
|
||
| ## Major Themes | ||
| In this release, we have continued to make important improvements to the Vitess project with over 200 PRs in several areas. Some of the major bug fixes and changes in behaviors are documented in the [Release Notes](https://github.com/vitessio/vitess/blob/master/doc/releasenotes/8_0_0_release_notes.md). Please read them carefully and report any issues via GitHub. We would like to highlight the following themes for this release. | ||
| Compatibility (MySQL, frameworks) | ||
|
|
||
| Our ongoing work to make sure that Vitess accepts all queries that MySQL accepts. In particular, work has focused on SET and information_schema queries. Reserved connections are still not on by default, and you might need to enable it to see all queries and frameworks well supported. | ||
|
|
||
| We are proud to announce that we have initial support for: | ||
| * WordPress | ||
| * MySQL Workbench | ||
| * SQLAlchemy | ||
| * Mycli | ||
| * Gorm | ||
| * Ruby on Rails - ActiveRecord | ||
| * JVM - JDBC and Hibernate | ||
| * Django | ||
| * JavaScript - TypeORM and Sequelize | ||
| * PyMySQL | ||
| * Rust MySQL | ||
|
|
||
| ### Migration | ||
| Performance and error metrics and improved logging related to VReplication workflows have been added for more visibility into operational issues. Additional vtctld commands VExec and Workflow allow easier inspection and manipulation of VReplication streams. | ||
|
|
||
| The VStream API was enhanced to provide more information for integration with change data capture platforms: the Debezium Vitess adapter uses this capability. | ||
|
|
||
| We have incorporated several small feature enhancements and bug-fixes based on the increased traction that VReplication saw both among early adopters and large production setups. | ||
|
|
||
| ## Usability | ||
| Ease of usability and accessibility are very important for the Vitess community. Usability improvements were another highlight received from the community. | ||
|
|
||
| ## Innovation | ||
| We continue to add integration of popular open-source tools and utilities on top of the Vitess’s dynamic framework. There are a few of these in this release we would like to highlight. | ||
|
|
||
| * VTorc : Integration of Orchestrator has continued and finally became part of Vitess. This proven open-source tool which has been the de-facto solution for MySQL failover mechanisms is now built into Vitess. Support is experimental in 8.0 and we will continue to harden it in future releases. | ||
| * [Online Schema Changes](https://vitess.io/docs/user-guides/schema-changes/): Understanding the ALTER TABLE problem and coming up with a solution using proven tools was our goal to achieve this release. We’re able to integrate both pt-online-schema-change and gh-ost to overcome major limitations for schema migrations. | ||
|
|
||
| There is a shortlist of incompatible changes in this release. We encourage you to spend a moment reading the release notes. | ||
|
|
||
| Please download [Vitess 8](https://github.com/vitessio/vitess/releases/tag/v8.0.0) and try it out! | ||
|
|
||
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.
This needs to be a heading.