-
Notifications
You must be signed in to change notification settings - Fork 358
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 Spanner libraries version 5.0.0-beta01 #11717
Conversation
Changes in Google.Cloud.Spanner.Data version 5.0.0-beta01: ### Bug fixes - Have SpannerTransaction check if it has been disposed before executing commands. ([commit c97a70a](c97a70a)) ### New features - Add leader routing support. ([commit eb2157a](eb2157a)) - Add FLOAT32 enum to TypeCode ([commit 18e6491](18e6491)) - Add proto descriptors for proto and enum types in create/update/get database ddl requests ([commit 7085e3f](7085e3f)) - Add max_commit_delay API ([commit 3984609](3984609)) - Add proto and enum types ([commit ea75989](ea75989)) - **BREAKING CHANGE** Support inline transactions. ([#11360](#11360)) - Add directed_read_option in spanner.proto ([commit 3b374e0](3b374e0)) - Add PG.OID type cod annotation ([commit a8662dc](a8662dc)) - Add autoscaling config to the instance proto ([commit 07022a6](07022a6)) - Add BatchWrite API ([commit 7a127d0](7a127d0)) ### Documentation improvements - Update the comment regarding eligible SQL shapes for PartitionQuery ([commit 1eb3d3e](1eb3d3e)) - Updated comment formatting ([commit 3b374e0](3b374e0)) BREAKING CHANGE: In supporting inline transactions the main breaking change is behavioral: transactions are not prewarmed, instead they are acquired as needed, mainly through inlining transaction creation in the first command that attempts to use a transaction. The method `Google.Cloud.Spanner.V1.PooledSession.WithFreshTransactionOrNewAsync` has been removed, as a transaction is not created by the session until command execution. Use instead `Google.Cloud.Spanner.V1.PooledSession.RefreshedOrNewAsync` which returns a new PooledSession instance that either represents the same session but with no transaction associated to it or a newly acquired session. Since transactions are not prewarmed, the session pool does not need to distinguish between read-only and read-write session/transaction pairs. In the statistics classes that may be used for diagnostic purposes all properties distinguising between read-only and read-write statistics have been removed. Similarly, `Google.Cloud.Spanner.V1.SessionPoolOptions.WriteSessionsFraction` has bee removed. Packages in this release: - Release Google.Cloud.Spanner.Admin.Database.V1 version 5.0.0-beta01 - Release Google.Cloud.Spanner.Admin.Instance.V1 version 5.0.0-beta01 - Release Google.Cloud.Spanner.Common.V1 version 5.0.0-beta01 - Release Google.Cloud.Spanner.Data version 5.0.0-beta01 - Release Google.Cloud.Spanner.V1 version 5.0.0-beta01
Pull request diff results Detecting changes for Google.Cloud.Spanner.Admin.Instance.V1 Detecting changes for Google.Cloud.Spanner.Common.V1 Detecting changes for Google.Cloud.Spanner.Data Detecting changes for Google.Cloud.Spanner.V1 Checking compatibility with previous releases Diff level: Minor Checking compatibility for Google.Cloud.Spanner.Admin.Instance.V1 version 5.0.0-beta01 Diff level: Minor Checking compatibility for Google.Cloud.Spanner.Common.V1 version 5.0.0-beta01 Checking compatibility for Google.Cloud.Spanner.Data version 5.0.0-beta01 Diff level: Minor Checking compatibility for Google.Cloud.Spanner.V1 version 5.0.0-beta01 Minor changes: Diff level: Major |
|
The release build has started; the log can be viewed here. |
Release build succeeded. |
Changes in Google.Cloud.Spanner.Data version 5.0.0-beta01:
Bug fixes
New features
Documentation improvements
BREAKING CHANGE: In supporting inline transactions the main breaking change is behavioral: transactions are not prewarmed, instead they are acquired as needed, mainly through inlining transaction creation in the first command that attempts to use a transaction. The method
Google.Cloud.Spanner.V1.PooledSession.WithFreshTransactionOrNewAsync
has been removed, as a transaction is not created by the session until command execution. Use insteadGoogle.Cloud.Spanner.V1.PooledSession.RefreshedOrNewAsync
which returns a new PooledSession instance that either represents the same session but with no transaction associated to it or a newly acquired session. Since transactions are not prewarmed, the session pool does not need to distinguish between read-only and read-write session/transaction pairs. In the statistics classes that may be used for diagnostic purposes all properties distinguising between read-only and read-write statistics have been removed. Similarly,Google.Cloud.Spanner.V1.SessionPoolOptions.WriteSessionsFraction
has bee removed.Packages in this release: