feat: [Dataproc] ROLLBACK: add support for new Dataproc features (#5890)

PiperOrigin-RevId: 511238112 Source-Link: googleapis/googleapis@d126575 Source-Link: googleapis/googleapis-gen@a338d04 Copy-Tag: eyJwIjoiRGF0YXByb2MvLk93bEJvdC55YW1sIiwiaCI6ImEzMzhkMDQzMTViNzlhODk5YjRkMmZhMzE0NjllNDY1OWVhMzIyZDAifQ==
googleapis · Mar 21, 2023 · 09eb6b0 · 09eb6b0
1 parent cf02ba4
commit 09eb6b0
Show file tree

Hide file tree

Showing 63 changed files with 484 additions and 1,417 deletions.
diff --git a/Dataproc/metadata/V1/Batches.php b/Dataproc/metadata/V1/Batches.php
diff --git a/Dataproc/metadata/V1/Clusters.php b/Dataproc/metadata/V1/Clusters.php
diff --git a/Dataproc/metadata/V1/Jobs.php b/Dataproc/metadata/V1/Jobs.php
diff --git a/Dataproc/metadata/V1/Operations.php b/Dataproc/metadata/V1/Operations.php
diff --git a/Dataproc/metadata/V1/Shared.php b/Dataproc/metadata/V1/Shared.php
diff --git a/Dataproc/samples/V1/AutoscalingPolicyServiceClient/create_autoscaling_policy.php b/Dataproc/samples/V1/AutoscalingPolicyServiceClient/create_autoscaling_policy.php
@@ -45,18 +45,18 @@
  *                                                              of the location has the following format:
  *                                                              `projects/{project_id}/locations/{location}`
  *                                                              Please see {@see AutoscalingPolicyServiceClient::regionName()} for help formatting this field.
- * @param float  $policyBasicAlgorithmYarnConfigScaleUpFactor   Fraction of average YARN pending memory in the last cooldown
- *                                                              period for which to add workers. A scale-up factor of 1.0 will result in
- *                                                              scaling up so that there is no pending memory remaining after the update
- *                                                              (more aggressive scaling). A scale-up factor closer to 0 will result in a
- *                                                              smaller magnitude of scaling up (less aggressive scaling). See [How
- *                                                              autoscaling
+ * @param float  $policyBasicAlgorithmYarnConfigScaleUpFactor   Fraction of average YARN pending memory in the last cooldown period
+ *                                                              for which to add workers. A scale-up factor of 1.0 will result in scaling
+ *                                                              up so that there is no pending memory remaining after the update (more
+ *                                                              aggressive scaling). A scale-up factor closer to 0 will result in a smaller
+ *                                                              magnitude of scaling up (less aggressive scaling).
+ *                                                              See [How autoscaling
  *                                                              works](https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
  *                                                              for more information.
  *
  *                                                              Bounds: [0.0, 1.0].
- * @param float  $policyBasicAlgorithmYarnConfigScaleDownFactor Fraction of average YARN pending memory in the last cooldown
- *                                                              period for which to remove workers. A scale-down factor of 1 will result in
+ * @param float  $policyBasicAlgorithmYarnConfigScaleDownFactor Fraction of average YARN pending memory in the last cooldown period
+ *                                                              for which to remove workers. A scale-down factor of 1 will result in
  *                                                              scaling down so that there is no available memory remaining after the
  *                                                              update (more aggressive scaling). A scale-down factor of 0 disables
  *                                                              removing workers, which can be beneficial for autoscaling a single job.

diff --git a/Dataproc/samples/V1/AutoscalingPolicyServiceClient/update_autoscaling_policy.php b/Dataproc/samples/V1/AutoscalingPolicyServiceClient/update_autoscaling_policy.php
@@ -37,18 +37,18 @@
  * Disabled check for update_mask, because all updates will be full
  * replacements.
  *
- * @param float $policyBasicAlgorithmYarnConfigScaleUpFactor   Fraction of average YARN pending memory in the last cooldown
- *                                                             period for which to add workers. A scale-up factor of 1.0 will result in
- *                                                             scaling up so that there is no pending memory remaining after the update
- *                                                             (more aggressive scaling). A scale-up factor closer to 0 will result in a
- *                                                             smaller magnitude of scaling up (less aggressive scaling). See [How
- *                                                             autoscaling
+ * @param float $policyBasicAlgorithmYarnConfigScaleUpFactor   Fraction of average YARN pending memory in the last cooldown period
+ *                                                             for which to add workers. A scale-up factor of 1.0 will result in scaling
+ *                                                             up so that there is no pending memory remaining after the update (more
+ *                                                             aggressive scaling). A scale-up factor closer to 0 will result in a smaller
+ *                                                             magnitude of scaling up (less aggressive scaling).
+ *                                                             See [How autoscaling
  *                                                             works](https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/autoscaling#how_autoscaling_works)
  *                                                             for more information.
  *
  *                                                             Bounds: [0.0, 1.0].
- * @param float $policyBasicAlgorithmYarnConfigScaleDownFactor Fraction of average YARN pending memory in the last cooldown
- *                                                             period for which to remove workers. A scale-down factor of 1 will result in
+ * @param float $policyBasicAlgorithmYarnConfigScaleDownFactor Fraction of average YARN pending memory in the last cooldown period
+ *                                                             for which to remove workers. A scale-down factor of 1 will result in
  *                                                             scaling down so that there is no available memory remaining after the
  *                                                             update (more aggressive scaling). A scale-down factor of 0 disables
  *                                                             removing workers, which can be beneficial for autoscaling a single job.

diff --git a/Dataproc/samples/V1/BatchControllerClient/delete_batch.php b/Dataproc/samples/V1/BatchControllerClient/delete_batch.php
@@ -30,10 +30,8 @@
  * Deletes the batch workload resource. If the batch is not in terminal state,
  * the delete fails and the response returns `FAILED_PRECONDITION`.
  *
- * @param string $formattedName The fully qualified name of the batch to retrieve
- *                              in the format
- *                              "projects/PROJECT_ID/locations/DATAPROC_REGION/batches/BATCH_ID"
- *                              Please see {@see BatchControllerClient::batchName()} for help formatting this field.
+ * @param string $formattedName The name of the batch resource to delete. Please see
+ *                              {@see BatchControllerClient::batchName()} for help formatting this field.
  */
 function delete_batch_sample(string $formattedName): void
 {

diff --git a/Dataproc/samples/V1/BatchControllerClient/get_batch.php b/Dataproc/samples/V1/BatchControllerClient/get_batch.php
@@ -30,10 +30,8 @@
 /**
  * Gets the batch workload resource representation.
  *
- * @param string $formattedName The fully qualified name of the batch to retrieve
- *                              in the format
- *                              "projects/PROJECT_ID/locations/DATAPROC_REGION/batches/BATCH_ID"
- *                              Please see {@see BatchControllerClient::batchName()} for help formatting this field.
+ * @param string $formattedName The name of the batch to retrieve. Please see
+ *                              {@see BatchControllerClient::batchName()} for help formatting this field.
  */
 function get_batch_sample(string $formattedName): void
 {

diff --git a/Dataproc/samples/V1/WorkflowTemplateServiceClient/create_workflow_template.php b/Dataproc/samples/V1/WorkflowTemplateServiceClient/create_workflow_template.php
@@ -49,8 +49,8 @@
  *
  *                                   The step id is used as prefix for job id, as job
  *                                   `goog-dataproc-workflow-step-id` label, and in
- *                                   [prerequisiteStepIds][google.cloud.dataproc.v1.OrderedJob.prerequisite_step_ids]
- *                                   field from other steps.
+ *                                   [prerequisiteStepIds][google.cloud.dataproc.v1.OrderedJob.prerequisite_step_ids] field from other
+ *                                   steps.
  *
  *                                   The id must contain only letters (a-z, A-Z), numbers (0-9),
  *                                   underscores (_), and hyphens (-). Cannot begin or end with underscore

diff --git a/Dataproc/samples/V1/WorkflowTemplateServiceClient/instantiate_inline_workflow_template.php b/Dataproc/samples/V1/WorkflowTemplateServiceClient/instantiate_inline_workflow_template.php
@@ -35,8 +35,7 @@
  * Instantiates a template and begins execution.
  *
  * This method is equivalent to executing the sequence
- * [CreateWorkflowTemplate][google.cloud.dataproc.v1.WorkflowTemplateService.CreateWorkflowTemplate],
- * [InstantiateWorkflowTemplate][google.cloud.dataproc.v1.WorkflowTemplateService.InstantiateWorkflowTemplate],
+ * [CreateWorkflowTemplate][google.cloud.dataproc.v1.WorkflowTemplateService.CreateWorkflowTemplate], [InstantiateWorkflowTemplate][google.cloud.dataproc.v1.WorkflowTemplateService.InstantiateWorkflowTemplate],
  * [DeleteWorkflowTemplate][google.cloud.dataproc.v1.WorkflowTemplateService.DeleteWorkflowTemplate].
  *
  * The returned Operation can be used to track execution of
@@ -75,8 +74,8 @@
  *
  *                                   The step id is used as prefix for job id, as job
  *                                   `goog-dataproc-workflow-step-id` label, and in
- *                                   [prerequisiteStepIds][google.cloud.dataproc.v1.OrderedJob.prerequisite_step_ids]
- *                                   field from other steps.
+ *                                   [prerequisiteStepIds][google.cloud.dataproc.v1.OrderedJob.prerequisite_step_ids] field from other
+ *                                   steps.
  *
  *                                   The id must contain only letters (a-z, A-Z), numbers (0-9),
  *                                   underscores (_), and hyphens (-). Cannot begin or end with underscore

diff --git a/Dataproc/samples/V1/WorkflowTemplateServiceClient/update_workflow_template.php b/Dataproc/samples/V1/WorkflowTemplateServiceClient/update_workflow_template.php
@@ -39,8 +39,8 @@
  *
  *                                   The step id is used as prefix for job id, as job
  *                                   `goog-dataproc-workflow-step-id` label, and in
- *                                   [prerequisiteStepIds][google.cloud.dataproc.v1.OrderedJob.prerequisite_step_ids]
- *                                   field from other steps.
+ *                                   [prerequisiteStepIds][google.cloud.dataproc.v1.OrderedJob.prerequisite_step_ids] field from other
+ *                                   steps.
  *
  *                                   The id must contain only letters (a-z, A-Z), numbers (0-9),
  *                                   underscores (_), and hyphens (-). Cannot begin or end with underscore

diff --git a/Dataproc/src/V1/AcceleratorConfig.php b/Dataproc/src/V1/AcceleratorConfig.php