Bump google-cloud-spanner from 0.24.0-beta to 1.6.0

[dependabot-preview]

Bumps google-cloud-spanner from 0.24.0-beta to 1.6.0.

Release notes

Sourced from google-cloud-spanner's releases.

v0.79.0

01-23-2019 11:57 PST

Asset

• Regenerate asset client (#4395)

Bigtable

• tableAdmin sample (#4313)

Compute

• Regenerate compute client (#4359)

Firestore

• Include a trailing /documents on root resource paths (#4352)

Spanner

• Regenerate spanner client (#4388)

Scheduler

• Regenerate scheduler client (#4294)
• Regenerate scheduler client (#4396)

v0.78.0

BigQuery

• BigQuery: Fix NPE for null table schema fields (#4338)

Bigtable

• Cloud Bigtable: HelloWorld sample updates (#4339)
• Bigtable: Fixing a typo for KeyOffSet#geyKey to getKey (#4342)
• Bigtable: Expose single row read settings (#4321)
• Bigtable: fix handling of unset rpc timeouts (#4323)
• separate properties for bigtable.project and bigtable.instance (#4346)

Compute

• Regenerate compute client (#4327)

Firestore

• Firestore: (BREAKING CHANGE) change timestampsInSnapshots default to true. (#4353)

Pub/Sub

• Pub/Sub: default values in batch settings comments (#4350)

Spanner

• Spanner: remove junit from compile dependencies (#4334)
• Regenerate spanner client (#4332)

Dependencies

• Update maven-surefire-plugin to 3.0.0-M3 to fix Java 8 classloader (#4344)

Documentation

• Regenerate clients with updated copyright year (#4382)

... (truncated)

Changelog

Sourced from google-cloud-spanner's changelog.

v0.33.0

BigQuery

• Fix spelling. The name "Bigquery" is some methods are now properly spelled "BigQuery".
• Job.getQueryResults now waits for the query to complete.
  • You no longer have to call Job.waitFor.
• BigQuery.getQueryResults(JobId) is replaced.
  • Instead of bigquery.getQueryResults(id), use bigquery.getJob(id).getQueryResults().
• BigQuery.query and Job.getQueryResults returns TableResult, not QueryResponse.
  • Instead of queryResponse.getResult().iterateAll(), use tableResult.iterateAll().
  • This change should make iterating large result sets significantly faster.
• BigQuery.listTableData and Table.list returns TableResult instead of Page<FieldValueList>.
  • This remains source-compatible, since TableResult implements Page<FieldValueList>.
  • TableResult allows inserting Shema into each iterated row.
  • TableResult.getTotalRows() can be called to obtain the total number of rows across pages.
• Various Job statistics are no longer available at QueryResponse.
  • Use BigQuery.getJob then Job.getStatistics instead.

v0.36.0

Pub/Sub

• TopicName is renamed to ProjectTopicName, and now inherits from a new base class TopicName
• TopicNameOneOf, ProjectNameType are deleted
  • TopicNameOneOf.parse(String): use TopicNames.parse(String) instead
  • To check the subtype of the new TopicName base class, use instanceof(...)
• SubscriptionName is renamed to ProjectSubscriptionName
• SnapshotName is renamed to ProjectSnapshotName
• Resource name helper methods are removed from request classes:
  • setProjectWithProjectName(myProject): use setProject(myProject.toString()) instead
  • setNameWithTopicName(myTopic): use setName(myTopic.toString()) instead
  • setTopicWithTopicName(myTopic): use setTopic(myTopic.toString()) instead
  • setNameWithSubscriptionName(mySubscription): use setName(mySubscription.toString()) instead
  • setSubscriptionWithSubscriptionName(mySubscription): use setSubscription(mySubscription.toString()) instead
  • setNameWithSnapshotName(mySnapshot): use setName(mySnapshot.toString()) instead
  • setSnapshotWithSnapshotName(mySnapshot): use setSnapshot(mySnapshot.toString()) instead
  • topic.getNameAsTopicName(): use ProjectTopicName.parse(topic.getName())
  • subscription.getTopicAsTopicNameOneof(): use TopicNames.parse(subscription.getTopic())
  • subscription.getNameAsSubscriptionName(): use ProjectSubscriptionName.parse(subscription.getName())
  • snapshot.getNameAsSnapshotName(): use ProjectSnapshotName.parse(snapshot.getName())

v0.44.0

Pub/Sub

The default flow control settings for Subscriber is changed.

• Previously it keeps combined size of outstanding messages below 20% of available memory.
  Now it keeps the number of outstanding messages less than or equal to 1000.
• Previously it opens one stream per available CPU.
  Now it opens one regardless of number of CPUs.

Slow message consumers will likely see better load-balancing across machines.
Because each machine pulls messages less eagerly, messages not yet pulled can be pulled by another machine.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.