ETL Processing on Google Cloud Using Dataflow and BigQuery (Python) Reviews

Kaushik P. · Reviewed over 7 years ago

Good

Hiranmayee N. · Reviewed over 7 years ago

good

Anusha B. · Reviewed over 7 years ago

Tesfaye M. · Reviewed over 7 years ago

Jon T. · Reviewed over 7 years ago

Alejandro A. · Reviewed over 7 years ago

Time is limited. VMs were not scaling due to Quota limits and hence processes were slow to complete the tasks.

Thomas S. · Reviewed over 7 years ago

Good

Deeksha g. · Reviewed over 7 years ago

Tirupathi Rao K. · Reviewed over 7 years ago

Good

Keerthi Hanuma B. · Reviewed over 7 years ago

Nicolas V. · Reviewed over 7 years ago

Juan Manuel M. · Reviewed over 7 years ago

Give a bit more information about the code in the lab

Dimitry V. · Reviewed over 7 years ago

Qiang L. · Reviewed over 7 years ago

Shambhu K. · Reviewed over 7 years ago

Ok. Slow VM

Olatunji A. · Reviewed over 7 years ago

need to set the project environment in the virtual environment.

Freddy I. · Reviewed almost 8 years ago

George D. · Reviewed almost 8 years ago

Nagendar R. · Reviewed almost 8 years ago

Amit M. · Reviewed almost 8 years ago

Dmytro I. · Reviewed almost 8 years ago

Difficulty understanding what the point of this was without reading through all of the Python code. It would be helpful to give more context in the task description.

Jeffrey N. · Reviewed almost 8 years ago

Lohith P. · Reviewed almost 8 years ago

Sudhindra S. · Reviewed almost 8 years ago

This lab is probably broken. In section "Run the Apache Beam Pipeline", the first script generates five errors on incompatibilities. For instance: "google-gax 0.15.16 has requirement future<0.17dev,>=0.16.0, but you'll have future 0.17.1 which is incompatible." De second script failed, the error message revealed that $PROJECT was lost (maybe that happened when the text editor moved the cloud shell to a different windows?) I succeeded after setting $PROJECT again. The second script also gave warnings on EOL of Python 2.7 Step 5 gave a troubling warning: "Autoscaling: Unable to reach resize target in zone us-central1-a. QUOTA_EXCEEDED: Quota 'SSD_TOTAL_GB' exceeded. Limit: 500.0 in region us-central1. " although it did finish (slow). Step 6 showed this message in output: "Resized worker pool to 1, though goal was 15. This could be a quota issue." Resulting table of step 6 looked like garbage, at least the first few columns (city, name, state etc.) all had the same contents ("Josh Smith" or "John Liu"...) which sounds wrong. In the end I did get the point, but a correct lab may have worked better.

Zweitze d. · Reviewed almost 8 years ago