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

Vinod G. · Reviewed 10 months ago

Camila Carolina N. · Reviewed 10 months ago

(1) time granted to complete the lab is insufficient because of incredibly slow runtimes of Dataflow. I was waiting for more than 12 minutes for the Dataflow Template run time and it did not complete before lab time-out (2) for whatever reason I was not granted a 'pass' for creating the JSON schema file and uploading it intio GCS. I can see the file there - yet still the lab indicates I did not complete.

Tom B. · Reviewed 10 months ago

Masahiko H. · Reviewed 10 months ago

Ramiro P. · Reviewed 10 months ago

Marius B. · Reviewed 10 months ago

Sujitha P. · Reviewed 10 months ago

Once you Finish Enable Notebooks API there is no New Notebook option due to this couldn't complete the lab, as when i did create a notebook could not enter text

Jo-deane B. · Reviewed 10 months ago

Once you Finish Enable Notebooks API there is no New Notebook option due to this couldn't complete the lab, as when i did create a notebook could not enter text

Jo-deane B. · Reviewed 10 months ago

Himal D. · Reviewed 10 months ago

can't type in terminal

Jenna F. · Reviewed 10 months ago

Siddhartha G. · Reviewed 10 months ago

the beginning tutorial does not match the GCP UI

Joao P. · Reviewed 10 months ago

This lab needs to be fixed badly. The commands take you to the wrong directory, apache beam needs to be installed manually before running the pipeline, and now this next part is pointing to the wrong directory again. If you want to use the lab as-is, move it to course on debugging. However, that's not what I am tryna spend my time doin today.

Adam C. · Reviewed 10 months ago

Natalia M. · Reviewed 10 months ago

Natalia M. · Reviewed 10 months ago

Sivaramakrishnan C. · Reviewed 10 months ago

stucked in Jupiter Notebook - Terminal. No response. Seems to be a known issue here in this course

Timo O. · Reviewed 10 months ago

Marcin K. · Reviewed 10 months ago

Nikita F. · Reviewed 10 months ago

Marcin K. · Reviewed 10 months ago

It might be some glitch in the backend

Carlos R. · Reviewed 10 months ago

Jupyterlab terminal won't accept input

Mark V. · Reviewed 10 months ago

Error in start Lab

Carlos R. · Reviewed 10 months ago

Terminal doesn't allow you to type commands like the lab implies, and the Dataflow UI has been updated so the steps in setup are out of date. Will restart the lab to see if the Jupyter terminal issue was a fluke and update the review if that resolves the issue. Update: Did not solve the issue. Managed to use GCE's ssh terminal to run most of the pipeline code, but then the lab wouldn't detect that my tables were in BQ. Overall, lab seems broken what with code snippets being incorrect, terminal in the notebook not allowing code execution, etc.

David C. · Reviewed 10 months ago