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

Rajesh A. · Reviewed about 1 year ago

SUDHEER B. · Reviewed about 1 year ago

Rafael dos Santos Souza R. · Reviewed about 1 year ago

Htut K. · Reviewed about 1 year ago

Ahmed A. · Reviewed about 1 year ago

ARTI M. · Reviewed about 1 year ago

Gowtham K. · Reviewed about 1 year ago

Giovanni K. · Reviewed about 1 year ago

Interesante y eso que soy novata en el asunto, el proceso de las 4 ultimas tareas donde se abría el editor, y luego desde la consola cloud shell se pegaba cierto código, para luego de 4-5 minutos ver en dataflow, y cuando aparecía exitoso (completo) verificar en bigquery para identificar que apareciera..., ayudó a hacer mas fluido el proceso

MARIALEJANDRA . M. · Reviewed about 1 year ago

Please give more guidance on the "why" behind why we are doing this steps in regards to ETL. For someone that might not have all the background knowledge yet, this would be super helpful. More context would be awesome.

Bekah M. · Reviewed about 1 year ago

Juan Pablo I. · Reviewed about 1 year ago

Vikyath P. · Reviewed about 1 year ago

LUIZ T. · Reviewed about 1 year ago

Oscar H. · Reviewed about 1 year ago

Kalaiselvi S. · Reviewed about 1 year ago

Niranjan U. · Reviewed about 1 year ago

Amirlan S. · Reviewed about 1 year ago

Jaime S. · Reviewed about 1 year ago

Amirlan S. · Reviewed about 1 year ago

Franklin C. · Reviewed about 1 year ago

Marek Z. · Reviewed about 1 year ago

Izzaldi I. · Reviewed about 1 year ago

Diego G. · Reviewed about 1 year ago

Let people know at the beginning the automated steps at the end require at least 15-20 minutes to wait just for automated processes - I spent too much time reading the code at the beginning/researching (as the instructions suggest) that I had to rush through the final 5 tasks. The lab should be at least an hour and a half because of that.

Jared S. · Reviewed about 1 year ago

Rajesh A. · Reviewed about 1 year ago