Migrating to google-cloud-video_intelligence 3.0
The 3.0 release of the google-cloud-video_intelligence client is a significant upgrade based on a next-gen code generator, and includes substantial interface changes. Existing code written for earlier versions of this library will likely require updates to use this version. This document describes the changes that have been made, and what you need to do to update your usage.
To summarize:
- The library has been broken out into multiple libraries. The new gems
google-cloud-video_intelligence-v1,google-cloud-video_intelligence-v1beta2,google-cloud-video_intelligence-v1p1beta1, andgoogle-cloud-video_intelligence-v1p2beta1contain the actual client classes for the various versions of the VideoIntelligence service, and the gemgoogle-cloud-video_intelligencenow simply provides a convenience wrapper. See Library Structure for more info. - The library uses a new configuration mechanism giving you closer control over endpoint address, network timeouts, and retry. See Client Configuration for more info. Furthermore, when creating a client object, you can customize its configuration in a block rather than passing arguments to the constructor. See Creating Clients for more info.
- Previously, positional arguments were used to indicate required arguments. Now, all method arguments are keyword arguments, with documentation that specifies whether they are required or optional. Additionally, you can pass a proto request object instead of separate arguments. See Passing Arguments for more info.
- Previously, clients reported RPC errors by raising instances of
Google::Gax::GaxErrorand its subclasses. Now, RPC exceptions are of typeGoogle::Cloud::Errorand its subclasses. See Handling Errors for more info. - Some classes have moved into different namespaces. See Class Namespaces for more info.
Library Structure
Older releases of the google-cloud-video_intelligence gem were all-in-one gems that included potentially multiple clients for multiple versions of the Video Intelligence service. The Google::Cloud::VideoIntelligence.new factory method would return you an instance of a Google::Cloud::VideoIntelligence::V1::VideoIntelligenceServiceClient object for the V1 version of the service, (or other corresponding classes for other versions of the service). All these classes were defined in the same gem.
With the 3.0 release, the google-cloud-video_intelligence gem still provides factory methods for obtaining clients. (The method signatures will have changed. See Creating Clients for details.) However, the actual client classes have been moved into separate gems, one per service version. The Google::Cloud::VideoIntelligence::V1::VideoIntelligenceService::Client class, along with its helpers and data types, is now part of the google-cloud-video_intelligence-v1 gem. Corresponding classes for other versions of the service are similarly moved to other gems with the version in the gem name.
For normal usage, you can continue to install the google-cloud-video_intelligence gem (which will bring in the versioned client gems as dependencies) and continue to use factory methods to create clients. However, you may alternatively choose to install only one of the versioned gems. For example, if you know you will only use V1 of the service, you can install google-cloud-video_intelligence-v1 by itself, and construct instances of the Google::Cloud::VideoIntelligence::V1::VideoIntelligenceService::Client client class directly.
Client Configuration
In older releases, if you wanted to customize performance parameters or low-level behavior of the client (such as credentials, timeouts, or instrumentation), you would pass a variety of keyword arguments to the client constructor. It was also extremely difficult to customize the default settings.
With the 3.0 release, a configuration interface provides control over these parameters, including defaults for all instances of a client, and settings for each specific client instance. For example, to set default credentials and timeout for all Speech V1 clients:
Google::Cloud::VideoIntelligence::V1::VideoIntelligenceService::Client.configure do |config| config.credentials = "/path/to/credentials.json" config.timeout = 10.0 end Individual RPCs can also be configured independently. For example, to set the timeout for the annotate_video call:
Google::Cloud::VideoIntelligence::V1::VideoIntelligenceService::Client.configure do |config| config.rpcs.annotate_video.timeout = 20.0 end Defaults for certain configurations can be set for all Video Intelligence versions and services globally:
Google::Cloud::VideoIntelligence.configure do |config| config.credentials = "/path/to/credentials.json" config.timeout = 10.0 end Finally, you can override the configuration for each client instance. See the next section on Creating Clients for details.
Creating Clients
In older releases, to create a client object, you would use the Google::Cloud::VideoIntelligence.new class method. Keyword arguments were available to select a service version and to configure parameters such as credentials and timeouts.
With the 3.0 release, use the Google::Cloud::VideoIntelligence.video_intelligence_service class method to create a client object. You may select a service version using the :version keyword argument. However, other configuration parameters should be set in a configuration block when you create the client.
Old:
client = Google::Cloud::VideoIntelligence.new credentials: "/path/to/credentials.json" New:
client = Google::Cloud::VideoIntelligence.video_intelligence_service do |config| config.credentials = "/path/to/credentials.json" end The configuration block is optional. If you do not provide it, or you do not set some configuration parameters, then the default configuration is used. See Client Configuration.
Passing Arguments
In older releases, required arguments would be passed as positional method arguments, while most optional arguments would be passed as keyword arguments.
With the 3.0 release, all RPC arguments are passed as keyword arguments, regardless of whether they are required or optional. For example:
Old:
client = Google::Cloud::VideoIntelligence.new features = [Google::Cloud::VideoIntelligence::V1::Feature::FACE_DETECTION] input_uri = "gs://my-bucket/my-video" # features is a positional argument, but input_uri is a keyword argument response = client.annotate_video features, input_uri: input_uri New:
client = Google::Cloud::VideoIntelligence.video_intelligence_service features = [Google::Cloud::VideoIntelligence::V1::Feature::FACE_DETECTION] input_uri = "gs://my-bucket/my-video" # features and input_uri are both keyword arguments response = client.annotate_video features: features, input_uri: input_uri In the 3.0 release, it is also possible to pass a request object, either as a hash or as a protocol buffer.
New:
client = Google::Cloud::VideoIntelligence.video_intelligence_service request = Google::Cloud::VideoIntelligence::V1::AnnotateVideoRequest.new( features: [Google::Cloud::VideoIntelligence::V1::Feature::FACE_DETECTION], input_uri: "gs://my-bucket/my-video" ) # Pass a request object as a positional argument: response = client.annotate_video request Finally, in older releases, to provide call options, you would pass a Google::Gax::CallOptions object with the :options keyword argument. In the 3.0 release, pass call options using a second set of keyword arguments.
Old:
client = Google::Cloud::VideoIntelligence.new features = [Google::Cloud::VideoIntelligence::V1::Feature::FACE_DETECTION] input_uri = "gs://my-bucket/my-video" options = Google::Gax::CallOptions.new timeout: 10.0 response = client.annotate_video features, input_uri: input_uri, options: options New:
client = Google::Cloud::VideoIntelligence.video_intelligence_service features = [Google::Cloud::VideoIntelligence::V1::Feature::FACE_DETECTION] input_uri = "gs://my-bucket/my-video" # Use a hash to wrap the normal call arguments (or pass a request object), and # then add further keyword arguments for the call options. response = client.annotate_video( { features: features, input_uri: input_uri }, timeout: 10.0) Handling Errors
The client reports standard gRPC error codes by raising exceptions. In older releases, these exceptions were located in the Google::Gax namespace and were subclasses of the Google::Gax::GaxError base exception class, defined in the google-gax gem. However, these classes were different from the standard exceptions (subclasses of Google::Cloud::Error) thrown by other client libraries such as google-cloud-storage.
The 3.0 client library now uses the Google::Cloud::Error exception hierarchy, for consistency across all the Google Cloud client libraries. In general, these exceptions have the same name as their counterparts from older releases, but are located in the Google::Cloud namespace rather than the Google::Gax namespace.
Old:
client = Google::Cloud::VideoIntelligence.new features = [Google::Cloud::VideoIntelligence::V1::Feature::FACE_DETECTION] input_uri = "gs://my-bucket/my-video" begin response = client.annotate_video features, input_uri: input_uri rescue Google::Gax::Error => e # Handle exceptions that subclass Google::Gax::Error end New:
client = Google::Cloud::VideoIntelligence.video_intelligence_service features = [Google::Cloud::VideoIntelligence::V1::Feature::FACE_DETECTION] input_uri = "gs://my-bucket/my-video" begin response = client.annotate_video features: features, input_uri: input_uri rescue Google::Cloud::Error => e # Handle exceptions that subclass Google::Cloud::Error end Class Namespaces
In some significantly older releases, (protobuf) data type classes were located in the namespace Google::Cloud::Videointelligence::V1 (note the lower-case "i".) In more recent releases, these were moved into Google::Cloud::VideoIntelligence::V1 (with an upper-case "I"), but the older namespace also continued to work. In the 3.0 release, the old namespace with a lower-case "i" has been dropped.
In older releases, the client object was of classes with names like: Google::Cloud::VideoIntelligence::V1::VideoIntelligenceServiceClient. In the 3.0 release, the client object is of a different class: Google::Cloud::VideoIntelligence::V1::VideoIntelligenceService::Client. Note that most users will use the factory methods such as Google::Cloud::VideoIntelligence.video_intelligence_service to create instances of the client object, so you may not need to reference the actual class directly. See Creating Clients.
In older releases, the credentials object was of class Google::Cloud::VideoIntelligence::V1::Credentials. In the 3.0 release, each service has its own credentials class, e.g. Google::Cloud::VideoIntelligence::V1::VideoIntelligenceService::Credentials. Again, most users will not need to reference this class directly. See Client Configuration.