From c250c84335281c7c4af319f8c56795477936b214 Mon Sep 17 00:00:00 2001 From: yoshi-automation Date: Fri, 5 Jun 2020 06:17:33 -0700 Subject: [PATCH 1/7] changes without context autosynth cannot find the source of changes triggered by earlier changes in this repository, or by version upgrades to tools such as linters. --- google/cloud/dataproc_v1/proto/clusters_pb2.py | 10 +++++----- synth.metadata | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/google/cloud/dataproc_v1/proto/clusters_pb2.py b/google/cloud/dataproc_v1/proto/clusters_pb2.py index 6d084067..cdfe0bc3 100644 --- a/google/cloud/dataproc_v1/proto/clusters_pb2.py +++ b/google/cloud/dataproc_v1/proto/clusters_pb2.py @@ -3353,11 +3353,11 @@ completed. By default, executables are run on master and all worker nodes. You can test a node’s ``role`` metadata to run an executable on a master or worker node, as shown below using - ``curl`` (you can also use ``wget``): :: ROLE=$(curl -H - Metadata-Flavor:Google http://metadata/computeMetadata/v1/i - nstance/attributes/dataproc-role) if [[ "${ROLE}" == - 'Master' ]]; then ... master specific actions ... else - ... worker specific actions ... fi + ``curl`` (you can also use ``wget``): ROLE=\ :math:`(curl -H + Metadata-Flavor:Google http://metadata/computeMetadata/v1/ins + tance/attributes/dataproc-role) if [[ "`\ {ROLE}" == ‘Master’ + ]]; then … master specific actions … else … worker specific + actions … fi encryption_config: Optional. Encryption settings for the cluster. autoscaling_config: diff --git a/synth.metadata b/synth.metadata index 7a7844c7..2b01ec86 100644 --- a/synth.metadata +++ b/synth.metadata @@ -4,7 +4,7 @@ "git": { "name": ".", "remote": "https://github.com/googleapis/python-dataproc.git", - "sha": "40579d265c7c97febcfdec5f79b12ded8c232226" + "sha": "2021ceb663c17ccda395fcb7c672a889f7c03526" } }, { From 6631f71bbed5da8a9ab9ba4848761d93e19ca693 Mon Sep 17 00:00:00 2001 From: yoshi-automation Date: Fri, 5 Jun 2020 06:19:24 -0700 Subject: [PATCH 2/7] fix: autosynth for nodejs-apiary * fix: autosynth for nodejs-apiary A configuration file was lost during the copy from gerrit to github. * chore: remove old copy of node-apiary.yaml Source-Author: Jeffrey Rennie Source-Date: Tue May 19 16:51:15 2020 -0700 Source-Repo: googleapis/synthtool Source-Sha: 274dd49554809834287c24b6dd324a85283f1182 Source-Link: https://github.com/googleapis/synthtool/commit/274dd49554809834287c24b6dd324a85283f1182 --- google/cloud/dataproc_v1/proto/clusters_pb2.py | 10 +++++----- synth.metadata | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/google/cloud/dataproc_v1/proto/clusters_pb2.py b/google/cloud/dataproc_v1/proto/clusters_pb2.py index cdfe0bc3..6d084067 100644 --- a/google/cloud/dataproc_v1/proto/clusters_pb2.py +++ b/google/cloud/dataproc_v1/proto/clusters_pb2.py @@ -3353,11 +3353,11 @@ completed. By default, executables are run on master and all worker nodes. You can test a node’s ``role`` metadata to run an executable on a master or worker node, as shown below using - ``curl`` (you can also use ``wget``): ROLE=\ :math:`(curl -H - Metadata-Flavor:Google http://metadata/computeMetadata/v1/ins - tance/attributes/dataproc-role) if [[ "`\ {ROLE}" == ‘Master’ - ]]; then … master specific actions … else … worker specific - actions … fi + ``curl`` (you can also use ``wget``): :: ROLE=$(curl -H + Metadata-Flavor:Google http://metadata/computeMetadata/v1/i + nstance/attributes/dataproc-role) if [[ "${ROLE}" == + 'Master' ]]; then ... master specific actions ... else + ... worker specific actions ... fi encryption_config: Optional. Encryption settings for the cluster. autoscaling_config: diff --git a/synth.metadata b/synth.metadata index 2b01ec86..7a7844c7 100644 --- a/synth.metadata +++ b/synth.metadata @@ -4,7 +4,7 @@ "git": { "name": ".", "remote": "https://github.com/googleapis/python-dataproc.git", - "sha": "2021ceb663c17ccda395fcb7c672a889f7c03526" + "sha": "40579d265c7c97febcfdec5f79b12ded8c232226" } }, { From 9c04802bd3bafc8ced2ed69e055465601fadb1c7 Mon Sep 17 00:00:00 2001 From: yoshi-automation Date: Fri, 5 Jun 2020 06:20:40 -0700 Subject: [PATCH 3/7] docs: change relative URLs to absolute URLs to fix broken links. PiperOrigin-RevId: 314634470 Source-Author: Google APIs Source-Date: Wed Jun 3 17:15:00 2020 -0700 Source-Repo: googleapis/googleapis Source-Sha: c1fae183ddeef0c59538863eac611fd679d1b7fb Source-Link: https://github.com/googleapis/googleapis/commit/c1fae183ddeef0c59538863eac611fd679d1b7fb --- google/cloud/dataproc_v1/proto/clusters_pb2.py | 10 +++++----- google/cloud/dataproc_v1/proto/jobs.proto | 5 +++-- google/cloud/dataproc_v1/proto/jobs_pb2.py | 5 +++-- google/cloud/dataproc_v1beta2/proto/jobs.proto | 5 +++-- google/cloud/dataproc_v1beta2/proto/jobs_pb2.py | 5 +++-- synth.metadata | 6 +++--- 6 files changed, 20 insertions(+), 16 deletions(-) diff --git a/google/cloud/dataproc_v1/proto/clusters_pb2.py b/google/cloud/dataproc_v1/proto/clusters_pb2.py index 6d084067..cdfe0bc3 100644 --- a/google/cloud/dataproc_v1/proto/clusters_pb2.py +++ b/google/cloud/dataproc_v1/proto/clusters_pb2.py @@ -3353,11 +3353,11 @@ completed. By default, executables are run on master and all worker nodes. You can test a node’s ``role`` metadata to run an executable on a master or worker node, as shown below using - ``curl`` (you can also use ``wget``): :: ROLE=$(curl -H - Metadata-Flavor:Google http://metadata/computeMetadata/v1/i - nstance/attributes/dataproc-role) if [[ "${ROLE}" == - 'Master' ]]; then ... master specific actions ... else - ... worker specific actions ... fi + ``curl`` (you can also use ``wget``): ROLE=\ :math:`(curl -H + Metadata-Flavor:Google http://metadata/computeMetadata/v1/ins + tance/attributes/dataproc-role) if [[ "`\ {ROLE}" == ‘Master’ + ]]; then … master specific actions … else … worker specific + actions … fi encryption_config: Optional. Encryption settings for the cluster. autoscaling_config: diff --git a/google/cloud/dataproc_v1/proto/jobs.proto b/google/cloud/dataproc_v1/proto/jobs.proto index 0379c09d..b9026f62 100644 --- a/google/cloud/dataproc_v1/proto/jobs.proto +++ b/google/cloud/dataproc_v1/proto/jobs.proto @@ -435,8 +435,9 @@ message SparkRJob { // A Dataproc job for running [Presto](https://prestosql.io/) queries. // **IMPORTANT**: The [Dataproc Presto Optional -// Component](/dataproc/docs/concepts/components/presto) must be enabled when -// the cluster is created to submit a Presto job to the cluster. +// Component](https://cloud.google.com/dataproc/docs/concepts/components/presto) +// must be enabled when the cluster is created to submit a Presto job to the +// cluster. message PrestoJob { // Required. The sequence of Presto queries to execute, specified as // either an HCFS file URI or as a list of queries. diff --git a/google/cloud/dataproc_v1/proto/jobs_pb2.py b/google/cloud/dataproc_v1/proto/jobs_pb2.py index 5eff1116..145d9007 100644 --- a/google/cloud/dataproc_v1/proto/jobs_pb2.py +++ b/google/cloud/dataproc_v1/proto/jobs_pb2.py @@ -4718,8 +4718,9 @@ "__module__": "google.cloud.dataproc_v1.proto.jobs_pb2", "__doc__": """A Dataproc job for running `Presto `__ queries. **IMPORTANT**: The `Dataproc Presto Optional Component - `__ must be enabled when - the cluster is created to submit a Presto job to the cluster. + `__ + must be enabled when the cluster is created to submit a Presto job to + the cluster. Attributes: queries: Required. The sequence of Presto queries to execute, specified diff --git a/google/cloud/dataproc_v1beta2/proto/jobs.proto b/google/cloud/dataproc_v1beta2/proto/jobs.proto index 325dc9e5..9d9aaae0 100644 --- a/google/cloud/dataproc_v1beta2/proto/jobs.proto +++ b/google/cloud/dataproc_v1beta2/proto/jobs.proto @@ -435,8 +435,9 @@ message SparkRJob { // A Dataproc job for running [Presto](https://prestosql.io/) queries. // **IMPORTANT**: The [Dataproc Presto Optional -// Component](/dataproc/docs/concepts/components/presto) must be enabled when -// the cluster is created to submit a Presto job to the cluster. +// Component](https://cloud.google.com/dataproc/docs/concepts/components/presto) +// must be enabled when the cluster is created to submit a Presto job to the +// cluster. message PrestoJob { // Required. The sequence of Presto queries to execute, specified as // either an HCFS file URI or as a list of queries. diff --git a/google/cloud/dataproc_v1beta2/proto/jobs_pb2.py b/google/cloud/dataproc_v1beta2/proto/jobs_pb2.py index d50ac093..f7737363 100644 --- a/google/cloud/dataproc_v1beta2/proto/jobs_pb2.py +++ b/google/cloud/dataproc_v1beta2/proto/jobs_pb2.py @@ -4735,8 +4735,9 @@ class or the main class name. To pass both a main jar and a main class "__module__": "google.cloud.dataproc_v1beta2.proto.jobs_pb2", "__doc__": """A Dataproc job for running `Presto `__ queries. **IMPORTANT**: The `Dataproc Presto Optional Component - `__ must be enabled when - the cluster is created to submit a Presto job to the cluster. + `__ + must be enabled when the cluster is created to submit a Presto job to + the cluster. Attributes: queries: Required. The sequence of Presto queries to execute, specified diff --git a/synth.metadata b/synth.metadata index 7a7844c7..f7858769 100644 --- a/synth.metadata +++ b/synth.metadata @@ -4,15 +4,15 @@ "git": { "name": ".", "remote": "https://github.com/googleapis/python-dataproc.git", - "sha": "40579d265c7c97febcfdec5f79b12ded8c232226" + "sha": "2021ceb663c17ccda395fcb7c672a889f7c03526" } }, { "git": { "name": "googleapis", "remote": "https://github.com/googleapis/googleapis.git", - "sha": "3a4894c4f0da3e763aca2c67bd280ae915177450", - "internalRef": "314363155" + "sha": "c1fae183ddeef0c59538863eac611fd679d1b7fb", + "internalRef": "314634470" } }, { From 35aecc7b5c2783ebf030418716cfd31e743d969d Mon Sep 17 00:00:00 2001 From: yoshi-automation Date: Fri, 5 Jun 2020 06:20:40 -0700 Subject: [PATCH 4/7] fix: Fix Recommendationengine bazel dependencies Without this fix the java_proto_library generates another copy of com.google.api.HttpBody, which causes a problem because this class is already included in the common java library. PiperOrigin-RevId: 314672365 Source-Author: Google APIs Source-Date: Wed Jun 3 22:57:39 2020 -0700 Source-Repo: googleapis/googleapis Source-Sha: 8dbe1d7f963adba47ea88205cae3ff6b97adb75e Source-Link: https://github.com/googleapis/googleapis/commit/8dbe1d7f963adba47ea88205cae3ff6b97adb75e --- google/cloud/dataproc_v1/proto/clusters_pb2.py | 10 +++++----- synth.metadata | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/google/cloud/dataproc_v1/proto/clusters_pb2.py b/google/cloud/dataproc_v1/proto/clusters_pb2.py index cdfe0bc3..6d084067 100644 --- a/google/cloud/dataproc_v1/proto/clusters_pb2.py +++ b/google/cloud/dataproc_v1/proto/clusters_pb2.py @@ -3353,11 +3353,11 @@ completed. By default, executables are run on master and all worker nodes. You can test a node’s ``role`` metadata to run an executable on a master or worker node, as shown below using - ``curl`` (you can also use ``wget``): ROLE=\ :math:`(curl -H - Metadata-Flavor:Google http://metadata/computeMetadata/v1/ins - tance/attributes/dataproc-role) if [[ "`\ {ROLE}" == ‘Master’ - ]]; then … master specific actions … else … worker specific - actions … fi + ``curl`` (you can also use ``wget``): :: ROLE=$(curl -H + Metadata-Flavor:Google http://metadata/computeMetadata/v1/i + nstance/attributes/dataproc-role) if [[ "${ROLE}" == + 'Master' ]]; then ... master specific actions ... else + ... worker specific actions ... fi encryption_config: Optional. Encryption settings for the cluster. autoscaling_config: diff --git a/synth.metadata b/synth.metadata index f7858769..e2e4f8bb 100644 --- a/synth.metadata +++ b/synth.metadata @@ -11,8 +11,8 @@ "git": { "name": "googleapis", "remote": "https://github.com/googleapis/googleapis.git", - "sha": "c1fae183ddeef0c59538863eac611fd679d1b7fb", - "internalRef": "314634470" + "sha": "8dbe1d7f963adba47ea88205cae3ff6b97adb75e", + "internalRef": "314672365" } }, { From d3d29348306890aa5326091fcfa4522330c36367 Mon Sep 17 00:00:00 2001 From: yoshi-automation Date: Fri, 5 Jun 2020 06:21:45 -0700 Subject: [PATCH 5/7] docs: change relative URLs to absolute URLs to fix broken links. PiperOrigin-RevId: 314725741 Source-Author: Google APIs Source-Date: Thu Jun 4 07:32:25 2020 -0700 Source-Repo: googleapis/googleapis Source-Sha: e45a2f54dce1ac68497acf305145f9e5bb7e1e48 Source-Link: https://github.com/googleapis/googleapis/commit/e45a2f54dce1ac68497acf305145f9e5bb7e1e48 --- google/cloud/dataproc_v1/proto/clusters_pb2.py | 10 +++++----- synth.metadata | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/google/cloud/dataproc_v1/proto/clusters_pb2.py b/google/cloud/dataproc_v1/proto/clusters_pb2.py index 6d084067..cdfe0bc3 100644 --- a/google/cloud/dataproc_v1/proto/clusters_pb2.py +++ b/google/cloud/dataproc_v1/proto/clusters_pb2.py @@ -3353,11 +3353,11 @@ completed. By default, executables are run on master and all worker nodes. You can test a node’s ``role`` metadata to run an executable on a master or worker node, as shown below using - ``curl`` (you can also use ``wget``): :: ROLE=$(curl -H - Metadata-Flavor:Google http://metadata/computeMetadata/v1/i - nstance/attributes/dataproc-role) if [[ "${ROLE}" == - 'Master' ]]; then ... master specific actions ... else - ... worker specific actions ... fi + ``curl`` (you can also use ``wget``): ROLE=\ :math:`(curl -H + Metadata-Flavor:Google http://metadata/computeMetadata/v1/ins + tance/attributes/dataproc-role) if [[ "`\ {ROLE}" == ‘Master’ + ]]; then … master specific actions … else … worker specific + actions … fi encryption_config: Optional. Encryption settings for the cluster. autoscaling_config: diff --git a/synth.metadata b/synth.metadata index e2e4f8bb..7ae655e0 100644 --- a/synth.metadata +++ b/synth.metadata @@ -11,8 +11,8 @@ "git": { "name": "googleapis", "remote": "https://github.com/googleapis/googleapis.git", - "sha": "8dbe1d7f963adba47ea88205cae3ff6b97adb75e", - "internalRef": "314672365" + "sha": "e45a2f54dce1ac68497acf305145f9e5bb7e1e48", + "internalRef": "314725741" } }, { From 1ed09973cbf76d25525623d733c99978338e1e48 Mon Sep 17 00:00:00 2001 From: yoshi-automation Date: Fri, 5 Jun 2020 06:22:32 -0700 Subject: [PATCH 6/7] fix: dataproc/v1 raise timeouts in gapic v2 PiperOrigin-RevId: 314840739 Source-Author: Google APIs Source-Date: Thu Jun 4 18:03:14 2020 -0700 Source-Repo: googleapis/googleapis Source-Sha: 150cfa0d994f9656c57eb4ed50f49c2f2add93f2 Source-Link: https://github.com/googleapis/googleapis/commit/150cfa0d994f9656c57eb4ed50f49c2f2add93f2 --- .../dataproc_v1/gapic/cluster_controller_client_config.py | 4 ++-- synth.metadata | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/google/cloud/dataproc_v1/gapic/cluster_controller_client_config.py b/google/cloud/dataproc_v1/gapic/cluster_controller_client_config.py index 17ed4faf..a1081c8d 100644 --- a/google/cloud/dataproc_v1/gapic/cluster_controller_client_config.py +++ b/google/cloud/dataproc_v1/gapic/cluster_controller_client_config.py @@ -10,9 +10,9 @@ "initial_retry_delay_millis": 100, "retry_delay_multiplier": 1.3, "max_retry_delay_millis": 60000, - "initial_rpc_timeout_millis": 10000, + "initial_rpc_timeout_millis": 30000, "rpc_timeout_multiplier": 1.0, - "max_rpc_timeout_millis": 10000, + "max_rpc_timeout_millis": 30000, "total_timeout_millis": 300000, } }, diff --git a/synth.metadata b/synth.metadata index 7ae655e0..43107dbe 100644 --- a/synth.metadata +++ b/synth.metadata @@ -11,8 +11,8 @@ "git": { "name": "googleapis", "remote": "https://github.com/googleapis/googleapis.git", - "sha": "e45a2f54dce1ac68497acf305145f9e5bb7e1e48", - "internalRef": "314725741" + "sha": "150cfa0d994f9656c57eb4ed50f49c2f2add93f2", + "internalRef": "314840739" } }, { From 9047b1140fe2a6f6b24e4bbcaae333568ec420a7 Mon Sep 17 00:00:00 2001 From: yoshi-automation Date: Fri, 5 Jun 2020 06:23:03 -0700 Subject: [PATCH 7/7] docs: cleaned docs for the Agents service and resource. PiperOrigin-RevId: 314879617 Source-Author: Google APIs Source-Date: Fri Jun 5 00:27:22 2020 -0700 Source-Repo: googleapis/googleapis Source-Sha: cd804bab06e46dd1a4f16c32155fd3cddb931b52 Source-Link: https://github.com/googleapis/googleapis/commit/cd804bab06e46dd1a4f16c32155fd3cddb931b52 --- google/cloud/dataproc_v1/proto/clusters_pb2.py | 10 +++++----- synth.metadata | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/google/cloud/dataproc_v1/proto/clusters_pb2.py b/google/cloud/dataproc_v1/proto/clusters_pb2.py index cdfe0bc3..6d084067 100644 --- a/google/cloud/dataproc_v1/proto/clusters_pb2.py +++ b/google/cloud/dataproc_v1/proto/clusters_pb2.py @@ -3353,11 +3353,11 @@ completed. By default, executables are run on master and all worker nodes. You can test a node’s ``role`` metadata to run an executable on a master or worker node, as shown below using - ``curl`` (you can also use ``wget``): ROLE=\ :math:`(curl -H - Metadata-Flavor:Google http://metadata/computeMetadata/v1/ins - tance/attributes/dataproc-role) if [[ "`\ {ROLE}" == ‘Master’ - ]]; then … master specific actions … else … worker specific - actions … fi + ``curl`` (you can also use ``wget``): :: ROLE=$(curl -H + Metadata-Flavor:Google http://metadata/computeMetadata/v1/i + nstance/attributes/dataproc-role) if [[ "${ROLE}" == + 'Master' ]]; then ... master specific actions ... else + ... worker specific actions ... fi encryption_config: Optional. Encryption settings for the cluster. autoscaling_config: diff --git a/synth.metadata b/synth.metadata index 43107dbe..3f04b2c8 100644 --- a/synth.metadata +++ b/synth.metadata @@ -11,8 +11,8 @@ "git": { "name": "googleapis", "remote": "https://github.com/googleapis/googleapis.git", - "sha": "150cfa0d994f9656c57eb4ed50f49c2f2add93f2", - "internalRef": "314840739" + "sha": "cd804bab06e46dd1a4f16c32155fd3cddb931b52", + "internalRef": "314879617" } }, {