fix(retail): update the API

#### retail:v2alpha The following keys were changed: - schemas.GoogleCloudRetailLoggingImportErrorContext.properties.gcsPath.description - schemas.GoogleCloudRetailV2alphaProduct.properties.attributes.description - schemas.GoogleCloudRetailV2alphaProduct.properties.type.description - schemas.GoogleCloudRetailV2alphaUserEvent.description #### retail:v2beta The following keys were changed: - schemas.GoogleCloudRetailLoggingImportErrorContext.properties.gcsPath.description - schemas.GoogleCloudRetailV2betaProduct.properties.attributes.description - schemas.GoogleCloudRetailV2betaProduct.properties.type.description - schemas.GoogleCloudRetailV2betaUserEvent.description #### retail:v2 The following keys were changed: - schemas.GoogleCloudRetailLoggingImportErrorContext.properties.gcsPath.description - schemas.GoogleCloudRetailV2Product.properties.attributes.description - schemas.GoogleCloudRetailV2Product.properties.type.description - schemas.GoogleCloudRetailV2UserEvent.description
googleapis · May 21, 2021 · a6cc2da · a6cc2da
1 parent 76890b7
commit a6cc2da
Show file tree

Hide file tree

Showing 6 changed files with 150 additions and 117 deletions.
diff --git a/discovery/retail-v2.json b/discovery/retail-v2.json
@@ -706,7 +706,7 @@
       }
     }
   },
-  "revision": "20210423",
+  "revision": "20210514",
   "rootUrl": "https://retail.googleapis.com/",
   "schemas": {
     "GoogleApiHttpBody": {
@@ -815,7 +815,7 @@
           "type": "string"
         },
         "gcsPath": {
-          "description": "GCS file path of the import source. Can be set for batch operation error.",
+          "description": "Cloud Storage file path of the import source. Can be set for batch operation error.",
           "type": "string"
         },
         "lineNumber": {
@@ -1220,7 +1220,7 @@
           "additionalProperties": {
             "$ref": "GoogleCloudRetailV2CustomAttribute"
           },
-          "description": "Highly encouraged. Extra product attributes to be included. For example, for products, this could include the store name, vendor, style, color, etc. These are very strong signals for recommendation model, thus we highly recommend providing the attributes here. Features that can take on one of a limited number of possible values. Two types of features can be set are: Textual features. some examples would be the brand/maker of a product, or country of a customer. Numerical features. Some examples would be the height/weight of a product, or age of a customer. For example: `{ \"vendor\": {\"text\": [\"vendor123\", \"vendor456\"]}, \"lengths_cm\": {\"numbers\":[2.3, 15.4]}, \"heights_cm\": {\"numbers\":[8.1, 6.4]} }`. This field needs to pass all below criteria, otherwise an INVALID_ARGUMENT error is returned: * Max entries count: 150 by default; 100 for Type.VARIANT. * The key must be a UTF-8 encoded string with a length limit of 128 characters.",
+          "description": "Highly encouraged. Extra product attributes to be included. For example, for products, this could include the store name, vendor, style, color, etc. These are very strong signals for recommendation model, thus we highly recommend providing the attributes here. Features that can take on one of a limited number of possible values. Two types of features can be set are: Textual features. some examples would be the brand/maker of a product, or country of a customer. Numerical features. Some examples would be the height/weight of a product, or age of a customer. For example: `{ \"vendor\": {\"text\": [\"vendor123\", \"vendor456\"]}, \"lengths_cm\": {\"numbers\":[2.3, 15.4]}, \"heights_cm\": {\"numbers\":[8.1, 6.4]} }`. This field needs to pass all below criteria, otherwise an INVALID_ARGUMENT error is returned: * Max entries count: 200 by default; 100 for Type.VARIANT. * The key must be a UTF-8 encoded string with a length limit of 128 characters.",
           "type": "object"
         },
         "availability": {
@@ -1297,7 +1297,7 @@
           "type": "string"
         },
         "type": {
-          "description": "Immutable. The type of the product. This field is output-only. Default to Catalog.product_level_config.ingestion_product_type if unset.",
+          "description": "Immutable. The type of the product. Default to Catalog.product_level_config.ingestion_product_type if unset.",
           "enum": [
             "TYPE_UNSPECIFIED",
             "PRIMARY",
@@ -1486,7 +1486,7 @@
       "type": "object"
     },
     "GoogleCloudRetailV2UserEvent": {
-      "description": "UserEvent captures all metadata information Retail API needs to know about how end users interact with customers' website. Next tag: 22",
+      "description": "UserEvent captures all metadata information Retail API needs to know about how end users interact with customers' website.",
       "id": "GoogleCloudRetailV2UserEvent",
       "properties": {
         "attributes": {

diff --git a/discovery/retail-v2alpha.json b/discovery/retail-v2alpha.json
@@ -706,7 +706,7 @@
       }
     }
   },
-  "revision": "20210423",
+  "revision": "20210514",
   "rootUrl": "https://retail.googleapis.com/",
   "schemas": {
     "GoogleApiHttpBody": {
@@ -815,7 +815,7 @@
           "type": "string"
         },
         "gcsPath": {
-          "description": "GCS file path of the import source. Can be set for batch operation error.",
+          "description": "Cloud Storage file path of the import source. Can be set for batch operation error.",
           "type": "string"
         },
         "lineNumber": {
@@ -1415,7 +1415,7 @@
           "additionalProperties": {
             "$ref": "GoogleCloudRetailV2alphaCustomAttribute"
           },
-          "description": "Highly encouraged. Extra product attributes to be included. For example, for products, this could include the store name, vendor, style, color, etc. These are very strong signals for recommendation model, thus we highly recommend providing the attributes here. Features that can take on one of a limited number of possible values. Two types of features can be set are: Textual features. some examples would be the brand/maker of a product, or country of a customer. Numerical features. Some examples would be the height/weight of a product, or age of a customer. For example: `{ \"vendor\": {\"text\": [\"vendor123\", \"vendor456\"]}, \"lengths_cm\": {\"numbers\":[2.3, 15.4]}, \"heights_cm\": {\"numbers\":[8.1, 6.4]} }`. This field needs to pass all below criteria, otherwise an INVALID_ARGUMENT error is returned: * Max entries count: 150 by default; 100 for Type.VARIANT. * The key must be a UTF-8 encoded string with a length limit of 128 characters.",
+          "description": "Highly encouraged. Extra product attributes to be included. For example, for products, this could include the store name, vendor, style, color, etc. These are very strong signals for recommendation model, thus we highly recommend providing the attributes here. Features that can take on one of a limited number of possible values. Two types of features can be set are: Textual features. some examples would be the brand/maker of a product, or country of a customer. Numerical features. Some examples would be the height/weight of a product, or age of a customer. For example: `{ \"vendor\": {\"text\": [\"vendor123\", \"vendor456\"]}, \"lengths_cm\": {\"numbers\":[2.3, 15.4]}, \"heights_cm\": {\"numbers\":[8.1, 6.4]} }`. This field needs to pass all below criteria, otherwise an INVALID_ARGUMENT error is returned: * Max entries count: 200 by default; 100 for Type.VARIANT. * The key must be a UTF-8 encoded string with a length limit of 128 characters.",
           "type": "object"
         },
         "availability": {
@@ -1492,7 +1492,7 @@
           "type": "string"
         },
         "type": {
-          "description": "Immutable. The type of the product. This field is output-only. Default to Catalog.product_level_config.ingestion_product_type if unset.",
+          "description": "Immutable. The type of the product. Default to Catalog.product_level_config.ingestion_product_type if unset.",
           "enum": [
             "TYPE_UNSPECIFIED",
             "PRIMARY",
@@ -1681,7 +1681,7 @@
       "type": "object"
     },
     "GoogleCloudRetailV2alphaUserEvent": {
-      "description": "UserEvent captures all metadata information Retail API needs to know about how end users interact with customers' website. Next tag: 22",
+      "description": "UserEvent captures all metadata information Retail API needs to know about how end users interact with customers' website.",
       "id": "GoogleCloudRetailV2alphaUserEvent",
       "properties": {
         "attributes": {

diff --git a/discovery/retail-v2beta.json b/discovery/retail-v2beta.json
@@ -706,7 +706,7 @@
       }
     }
   },
-  "revision": "20210423",
+  "revision": "20210514",
   "rootUrl": "https://retail.googleapis.com/",
   "schemas": {
     "GoogleApiHttpBody": {
@@ -815,7 +815,7 @@
           "type": "string"
         },
         "gcsPath": {
-          "description": "GCS file path of the import source. Can be set for batch operation error.",
+          "description": "Cloud Storage file path of the import source. Can be set for batch operation error.",
           "type": "string"
         },
         "lineNumber": {
@@ -1610,7 +1610,7 @@
           "additionalProperties": {
             "$ref": "GoogleCloudRetailV2betaCustomAttribute"
           },
-          "description": "Highly encouraged. Extra product attributes to be included. For example, for products, this could include the store name, vendor, style, color, etc. These are very strong signals for recommendation model, thus we highly recommend providing the attributes here. Features that can take on one of a limited number of possible values. Two types of features can be set are: Textual features. some examples would be the brand/maker of a product, or country of a customer. Numerical features. Some examples would be the height/weight of a product, or age of a customer. For example: `{ \"vendor\": {\"text\": [\"vendor123\", \"vendor456\"]}, \"lengths_cm\": {\"numbers\":[2.3, 15.4]}, \"heights_cm\": {\"numbers\":[8.1, 6.4]} }`. This field needs to pass all below criteria, otherwise an INVALID_ARGUMENT error is returned: * Max entries count: 150 by default; 100 for Type.VARIANT. * The key must be a UTF-8 encoded string with a length limit of 128 characters.",
+          "description": "Highly encouraged. Extra product attributes to be included. For example, for products, this could include the store name, vendor, style, color, etc. These are very strong signals for recommendation model, thus we highly recommend providing the attributes here. Features that can take on one of a limited number of possible values. Two types of features can be set are: Textual features. some examples would be the brand/maker of a product, or country of a customer. Numerical features. Some examples would be the height/weight of a product, or age of a customer. For example: `{ \"vendor\": {\"text\": [\"vendor123\", \"vendor456\"]}, \"lengths_cm\": {\"numbers\":[2.3, 15.4]}, \"heights_cm\": {\"numbers\":[8.1, 6.4]} }`. This field needs to pass all below criteria, otherwise an INVALID_ARGUMENT error is returned: * Max entries count: 200 by default; 100 for Type.VARIANT. * The key must be a UTF-8 encoded string with a length limit of 128 characters.",
           "type": "object"
         },
         "availability": {
@@ -1687,7 +1687,7 @@
           "type": "string"
         },
         "type": {
-          "description": "Immutable. The type of the product. This field is output-only. Default to Catalog.product_level_config.ingestion_product_type if unset.",
+          "description": "Immutable. The type of the product. Default to Catalog.product_level_config.ingestion_product_type if unset.",
           "enum": [
             "TYPE_UNSPECIFIED",
             "PRIMARY",
@@ -1876,7 +1876,7 @@
       "type": "object"
     },
     "GoogleCloudRetailV2betaUserEvent": {
-      "description": "UserEvent captures all metadata information Retail API needs to know about how end users interact with customers' website. Next tag: 22",
+      "description": "UserEvent captures all metadata information Retail API needs to know about how end users interact with customers' website.",
       "id": "GoogleCloudRetailV2betaUserEvent",
       "properties": {
         "attributes": {