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

Vinod G. · Sprawdzono ponad 2 lata temu

Camila Carolina N. · Sprawdzono ponad 2 lata temu

(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. · Sprawdzono ponad 2 lata temu

Masahiko H. · Sprawdzono ponad 2 lata temu

Ramiro P. · Sprawdzono ponad 2 lata temu

Marius B. · Sprawdzono ponad 2 lata temu

Sujitha P. · Sprawdzono ponad 2 lata temu

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

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

Himal D. · Sprawdzono ponad 2 lata temu

can't type in terminal

Jenna F. · Sprawdzono ponad 2 lata temu

Siddhartha G. · Sprawdzono ponad 2 lata temu

the beginning tutorial does not match the GCP UI

Joao P. · Sprawdzono ponad 2 lata temu

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

Natalia M. · Sprawdzono ponad 2 lata temu

Natalia M. · Sprawdzono ponad 2 lata temu

Sivaramakrishnan C. · Sprawdzono ponad 2 lata temu

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

Timo O. · Sprawdzono ponad 2 lata temu

Marcin K. · Sprawdzono ponad 2 lata temu

Nikita F. · Sprawdzono ponad 2 lata temu

Marcin K. · Sprawdzono ponad 2 lata temu

It might be some glitch in the backend

Carlos R. · Sprawdzono ponad 2 lata temu

Jupyterlab terminal won't accept input

Mark V. · Sprawdzono ponad 2 lata temu

Error in start Lab

Carlos R. · Sprawdzono ponad 2 lata temu

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