Skip to content

v1.16.0 Release

Choose a tag to compare

@mr-salty mr-salty released this 04 Aug 04:21
2a0aeef

Bigtable

  • doc: remove not GA warning from bigtable backup methods (#4601)
  • doc: restore quickstart's region tags (#4525)
  • fix: builds on 64-bit Windows (#4523)
  • fix: warnings under Windows+MSVC+x86 (#4515)
  • feat: CompletionQueue::RunAsync with no arguments (#4450)

Storage

BREAKING CHANGES

  • fix!: incorrect type in OLM condition (#4597)
    changed the created_before field in LifecycleRuleCondition from a time
    point to a date

Other Changes

  • fix: GCE credentials response handling (#4739)
  • feat: add a function to delete resumable upload in client (#4696)
  • doc: include guidelines for bucket names (#4688)
  • feat: add a function DeleteResumableUpload to RawClient (#4678)
  • fix: missing CreateDefaultClientOptions overload (#4677)
  • feat: a request type to delete pending resumable uploads (#4617)
  • feat: disable MD5Hash by default (#4591)
  • feat: Add startOffset and endOffset (#4518)
  • fix: warnings under Windows+MSVC+x86 (#4515)
  • fix: avoid chunked transfer encoding (#4506)
  • fix: avoid unnecessary chunk to finalize uploads (#4504)
  • feat: Add Client::ListObjectsAndPrefixes (#4494)
  • fix: multiple problems under Windows+MSVC+x86 (#4502)
  • feat: reduce data copies in uploads (#4496)
  • fix: workaround min/max macros on Windows (#4490)
  • feat: reduce copies during uploads (#4489)
  • feat: Add UploadFromOffset and UploadLimit to UploadFile (#4473)
  • feat: HTTP requests with many buffers (#4480)
  • feat: Add value_or() to options params and headers (#4408)

Spanner

BREAKING CHANGES

  • refactor!: spanner::Timestamp implementing using absl::Time (#4625)
    spanner::Timestamp no longer allows construction from or conversion to
    a chrono time point with picosecond precision
  • refactor!: use absl::CivilDay for "date" type (#4600)
    absl::CivilDay's constructors are explicit (by design), where as the old
    spanner::Date 3-arg constructor was not explicit.

Fix issue #4516: atomicity is violated if the first operation in a RW
Transaction fails.

If this occurs, the library now explicitly begins a new transaction and
retries the failed operation. This ensures subsequent operations using the
same Transaction object are in fact executed in the same Spanner
transaction.

  • fix: begin a has_begin transaction in Rollback() (#4731)
  • fix: handle ExecuteBatchDml returning OK with no results (#4724)
  • fix: use the updated transaction id in ReadImpl (#4722)
  • fix: explicitly begin failed implicit begin transactions (#4706)
  • feat: handle invalid transactions in ConnectionImpl methods
  • feat: store a Status when invalidating Transactions (#4670)
  • feat: support moving a Transaction into an error state (#4545)

Other Changes

  • doc: note that NUMERIC columns are not yet available (#4738)
  • feat: add google-cloud-resource-prefix to non-admin operations (#4703)
  • fix: date formatting with negative years (#4614)
  • feat: add google::cloud::spanner::Numeric (#4418)
  • fix: warnings under Windows+MSVC+x86 (#4515)
  • feat: log the result for future<StatusOr<T>> (#4746)

Common libraries

BREAKING CHANGES

  • fix!: incorrect type in OLM condition (#4597)
    changed the created_before field in LifecycleRuleCondition from a time
    point to a date

Other Changes

  • fix: timestamp proto encoding works before the epoch and with extreme values (#4611)
  • feat: CompletionQueue::RunAsync with no arguments (#4450)
  • feat: log exceptions in example driver (#4453)