Get Model Result
Constructors
Types
Properties
etag
is used for optimistic concurrency control as a way to help prevent simultaneous updates of a model from overwriting each other. It is strongly suggested that systems make use of the etag
in the read-modify-write cycle to perform model updates in order to avoid race conditions: An etag
is returned in the response to GetModel
, and systems are expected to put that etag in the request to UpdateModel
to ensure that their change will be applied to the model as intended.
Optional. If true, online prediction nodes send stderr
and stdout
streams to Cloud Logging. These can be more verbose than the standard access logs (see onlinePredictionLogging
) and can incur higher cost. However, they are helpful for debugging. Note that /stackdriver/pricing, especially if your project receives prediction requests at a high QPS. Estimate your costs before enabling this option. Default is false.
Optional. If true, online prediction access logs are sent to Cloud Logging. These logs are like standard server access logs, containing information like timestamp and latency for each request. Note that /stackdriver/pricing, especially if your project receives prediction requests at a high queries per second rate (QPS). Estimate your costs before enabling this option. Default is false.
Optional. The list of regions where the model is going to be deployed. Only one region per model is supported. Defaults to 'us-central1' if nothing is set. See the available regions for AI Platform services. Note: * No matter where a model is deployed, it can always be accessed by users from anywhere, both for online and batch prediction. * The region for a batch prediction job is set by the region field when submitting the batch prediction job and does not take its value from this field.