Serverless Data Processing with Dataflow - Writing an ETL Pipeline using Apache Beam and Dataflow (Python) Reviews

constantly running out of resources tartup of the worker pool in zone us-east1-b failed to bring up any of the desired 1 workers. Please refer to https://cloud.google.com/dataflow/docs/guides/common-errors#worker-pool-failure for help troubleshooting. ZONE_RESOURCE_POOL_EXHAUSTED:

Johannes V. · Reviewed about 2 years ago

Yaswanth Kumar K. · Reviewed about 2 years ago

It was pretty hard to finish this lab, i had issues parsing the json file, the format was not right at first, I don't know what changed but I am pretty sure I got it right the first time but something in the json parser was raising and error. After that I had issues with resources availability. I had to repeat this lab 3 times and depend on luck to finally finish it. It was not a good experience. It was raising errors even after consulting the answer script.

Alexandre Bonfim M. · Reviewed about 2 years ago

Horrendous, worst lab ever, literally there were no workers in us-central1 and it destroyed all the pipelines, had to run on us-west1. Not onyl that, all the instructions were really bad

Thales R. · Reviewed about 2 years ago

Very badly explained and written

Isaac H. · Reviewed about 2 years ago

Agustin E. · Reviewed about 2 years ago

Isaac G. · Reviewed about 2 years ago

i got stuck and the linked solution was literally just an outline and contained no guidance on the transformation or writing pcollection *|:

brian w. · Reviewed about 2 years ago

Chandra M. · Reviewed about 2 years ago

jupyther notebook is not reachable

Philip T. · Reviewed about 2 years ago

Ashutosh M. · Reviewed about 2 years ago

Heejung K. · Reviewed about 2 years ago

Unclear instructions regarding the parameters of the job, like the schema and name of the table. Even after copying the code from the solution and running with DirectRunner, the Lab didn't accept the solution.

Eloy E. · Reviewed about 2 years ago

Krzysztof S. · Reviewed about 2 years ago

Carlos D. · Reviewed about 2 years ago

Booker B. · Reviewed about 2 years ago

bit more difficult to follow but good

Prashant P. · Reviewed about 2 years ago

Martin T. · Reviewed about 2 years ago

Jose I. R. · Reviewed about 2 years ago

terminal was not working

Vladas V. · Reviewed about 2 years ago

Esteban Pedro A. · Reviewed about 2 years ago

Eliton Daniel G. · Reviewed about 2 years ago

Eliton Daniel G. · Reviewed about 2 years ago

Eliton Daniel G. · Reviewed about 2 years ago

Vladas V. · Reviewed about 2 years ago