google-cloud-bigquery-data_transfer 1.1.1 → 1.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f560be68a20d593781730563bf1e02e2ae0e3a858e86a9d03f9ba4fd7b05c754
-  data.tar.gz: bd8405d44f50b8f8add77ee3ee63b2cc62050cb4c11cc30fbf1ebda6bd3135dd
+  metadata.gz: 60fe72e9254c54cb53dd4d6d56cc45d54e934c9389f544755150d8e7ee028775
+  data.tar.gz: d41696331280f7f5b5374987a4490980aa41ac3915164bd16f719c6303e0f7ac
 SHA512:
-  metadata.gz: d446ecfa37af8d6d4526b57ecb0ba4c0dc94bcbbd124acfdf0099ea0c26a5c1dba9763d60fe61fbe212005ede265d7e309903504dde9e32b2cf12cdda5c85b42
-  data.tar.gz: b483f699f9a61112ffb44ed8fc06ff0f2cf4738d4a8a48365768f2edea9e3fddf9fe6d6fb16a2efc2814a1e72fe0f57d96fc723bb0d6d85c1cf1c38fa292f77f
+  metadata.gz: 51fceb40215ebc1aaeadf63675f38fa50336234e904b8813e7c04d42d7ecef9f34355c664f3ec9eea2c9f38211accf2e677dc4951a6f500ff4e51d5a9dbc2cd1
+  data.tar.gz: fb3d993a15d0d2b4d8618ab6d15c1572db340d1d8bda9d33005e4b76fa99d5d850d1228b8c46763f05d19a28198c45a35c72bfca798c82103de916968d6590b3

data/README.md

@@ -6,9 +6,10 @@ Schedules queries and transfers external data from SaaS applications to Google B
 
 Actual client classes for the various versions of this API are defined in
 _versioned_ client gems, with names of the form `google-cloud-bigquery-data_transfer-v*`.
-The gem `google-cloud-bigquery-data_transfer` is a convenience wrapper library that brings the
+The gem `google-cloud-bigquery-data_transfer` is the main client library that brings the
 verisoned gems in as dependencies, and provides high-level methods for
-constructing clients.
+constructing clients. More information on versioned clients can be found below
+in the section titled *Which client should I use?*.
 
 View the [Client Library Documentation](https://googleapis.dev/ruby/google-cloud-bigquery-data_transfer/latest)
 for this library, google-cloud-bigquery-data_transfer, to see the convenience methods for
@@ -77,3 +78,61 @@ in security maintenance, and not end of life. Currently, this means Ruby 2.4
 and later. Older versions of Ruby _may_ still work, but are unsupported and not
 recommended. See https://www.ruby-lang.org/en/downloads/branches/ for details
 about the Ruby support schedule.
+
+## Which client should I use?
+
+Most modern Ruby client libraries for Google APIs come in two flavors: the main
+client library with a name such as `google-cloud-bigquery-data_transfer`,
+and lower-level _versioned_ client libraries with names such as
+`google-cloud-bigquery-data_transfer-v1`.
+_In most cases, you should install the main client._
+
+### What's the difference between the main client and a versioned client?
+
+A _versioned client_ provides a basic set of data types and client classes for
+a _single version_ of a specific service. (That is, for a service with multiple
+versions, there might be a separate versioned client for each service version.)
+Most versioned clients are written and maintained by a code generator.
+
+The _main client_ is designed to provide you with the _recommended_ client
+interfaces for the service. There will be only one main client for any given
+service, even a service with multiple versions. The main client includes
+factory methods for constructing the client objects we recommend for most
+users. In some cases, those will be classes provided by an underlying versioned
+client; in other cases, they will be handwritten higher-level client objects
+with additional capabilities, convenience methods, or best practices built in.
+Generally, the main client will default to a recommended service version,
+although in some cases you can override this if you need to talk to a specific
+service version.
+
+### Why would I want to use the main client?
+
+We recommend that most users install the main client gem for a service. You can
+identify this gem as the one _without_ a version in its name, e.g.
+`google-cloud-bigquery-data_transfer`.
+The main client is recommended because it will embody the best practices for
+accessing the service, and may also provide more convenient interfaces or
+tighter integration into frameworks and third-party libraries. In addition, the
+documentation and samples published by Google will generally demonstrate use of
+the main client.
+
+### Why would I want to use a versioned client?
+
+You can use a versioned client if you are content with a possibly lower-level
+class interface, you explicitly want to avoid features provided by the main
+client, or you want to access a specific service version not be covered by the
+main client. You can identify versioned client gems because the service version
+is part of the name, e.g. `google-cloud-bigquery-data_transfer-v1`.
+
+### What about the google-apis-<name> clients?
+
+Client library gems with names that begin with `google-apis-` are based on an
+older code generation technology. They talk to a REST/JSON backend (whereas
+most modern clients talk to a [gRPC](https://grpc.io/) backend) and they may
+not offer the same performance, features, and ease of use provided by more
+modern clients.
+
+The `google-apis-` clients have wide coverage across Google services, so you
+might need to use one if there is no modern client available for the service.
+However, if a modern client is available, we generally recommend it over the
+older `google-apis-` clients.

data/lib/google/cloud/bigquery/data_transfer/version.rb

@@ -21,7 +21,7 @@ module Google
   module Cloud
     module Bigquery
       module DataTransfer
-        VERSION = "1.1.1"
+        VERSION = "1.1.2"
       end
     end
   end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-cloud-bigquery-data_transfer
 version: !ruby/object:Gem::Version
-  version: 1.1.1
+  version: 1.1.2
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-01-20 00:00:00.000000000 Z
+date: 2021-02-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-cloud-bigquery-data_transfer-v1