Dataflow: Qwik Start - Template Ulasan

Oscar V. · Diulas sekitar 1 bulan lalu

cristian S. · Diulas sekitar 1 bulan lalu

Oscar Adrián F. · Diulas sekitar 1 bulan lalu

May thu K. · Diulas sekitar 1 bulan lalu

Vladimiros P. · Diulas sekitar 1 bulan lalu

Jerez T. · Diulas sekitar 1 bulan lalu

Shreyank N. · Diulas sekitar 1 bulan lalu

Eric J. · Diulas sekitar 1 bulan lalu

Mathala N. · Diulas sekitar 1 bulan lalu

K N. · Diulas sekitar 1 bulan lalu

ASHOK J. · Diulas sekitar 1 bulan lalu

Juan Esteban G. · Diulas sekitar 1 bulan lalu

Henrique V. · Diulas sekitar 1 bulan lalu

Diego Armando H. · Diulas sekitar 1 bulan lalu

SHAURYA P. · Diulas sekitar 1 bulan lalu

Following the instructions for steps 1 and 2 using gcloud resulted in an error "Failed to write a file to temp location 'gs://qwiklabs-gcp-02-836a3d71f078/temp'. Please make sure that the bucket for this directory exists, and that the project under which the workflow is running has the necessary permissions to write to it."

Eric H. · Diulas sekitar 1 bulan lalu

{ "textPayload": "Startup of the worker pool in europe-west4-c failed to bring up any of the desired 1 workers. This is likely a quota issue or a Compute Engine stockout. The service will retry. For troubleshooting steps, see https://cloud.google.com/dataflow/docs/guides/common-errors#worker-pool-failure for help troubleshooting. ZONE_RESOURCE_POOL_EXHAUSTED: Instance 'iotflow-03120747-pnlh-harness-qmt3' creation failed: The zone 'projects/qwiklabs-gcp-01-366a0d3f4d28/zones/europe-west4-c' does not have enough resources available to fulfill the request. Try a different zone, or try again later.", "insertId": "y53ek8b20", "resource": { "type": "dataflow_step", "labels": { "step_id": "", "job_name": "iotflow", "project_id": "qwiklabs-gcp-01-366a0d3f4d28", "job_id": "2026-03-12_07_47_19-15333010018577678863", "region": "europe-west4" } }, "timestamp": "2026-03-12T14:52:30.548137179Z", "severity": "ERROR", "labels": { "dataflow.googleapis.com/job_name": "iotflow", "dataflow.googleapis.com/job_id": "2026-03-12_07_47_19-15333010018577678863", "dataflow.googleapis.com/log_type": "system", "dataflow.googleapis.com/region": "europe-west4" }, "logName": "projects/qwiklabs-gcp-01-366a0d3f4d28/logs/dataflow.googleapis.com%2Fjob-message", "receiveTimestamp": "2026-03-12T14:52:31.773332464Z", "errorGroups": [ { "id": "COmfkOup6NPaOg" } ] }

Minna I. · Diulas sekitar 1 bulan lalu

ABHISHEK B. · Diulas sekitar 1 bulan lalu

Shreya S. · Diulas sekitar 1 bulan lalu

Dr.Benjmin Jashva M. · Diulas sekitar 1 bulan lalu

Akhila A. · Diulas sekitar 1 bulan lalu

Arjun R. · Diulas sekitar 1 bulan lalu

I want to point out that Task 3 should be removed entirely. Even though there is a note stating that it shouldn't be performed because it repeats Task 2, it makes the lab experience very confusing and unprofessional. Having a full task header and instructions that you are supposed to "skip" or "ignore" breaks the flow of the lab. As a user, it’s frustrating to read through instructions only to find out they are redundant. If the content is already covered in Task 2, Task 3 serves no purpose and only leads to unnecessary doubt.

Laura Sofía J. · Diulas sekitar 1 bulan lalu

Bhaskaruni A. · Diulas sekitar 1 bulan lalu

Giuseppe P. · Diulas sekitar 1 bulan lalu