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

Jonathan P. · Sprawdzono ponad rok temu

Sadibou S. · Sprawdzono ponad rok temu

Nur Izzati A. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu

Yaswanth Kumar K. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu

Very badly explained and written

I G. · Sprawdzono ponad rok temu

Agustin E. · Sprawdzono ponad rok temu

Isaac G. · Sprawdzono ponad rok temu

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

brian w. · Sprawdzono ponad rok temu

Chandra M. · Sprawdzono ponad rok temu

jupyther notebook is not reachable

Philip T. · Sprawdzono ponad rok temu

Ashutosh M. · Sprawdzono ponad rok temu

Heejung K. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu

Krzysztof S. · Sprawdzono ponad rok temu

Carlos D. · Sprawdzono ponad rok temu

Booker B. · Sprawdzono ponad rok temu

bit more difficult to follow but good

Prashant P. · Sprawdzono ponad rok temu

Martin T. · Sprawdzono ponad rok temu

Jose I. R. · Sprawdzono ponad rok temu

terminal was not working

Vladas V. · Sprawdzono ponad rok temu

Esteban Pedro A. · Sprawdzono ponad rok temu

Eliton Daniel G. · Sprawdzono ponad rok temu