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

Bellittieri S. · Reviewed 8 months ago

Rajesh A. · Reviewed 8 months ago

SUDHEER B. · Reviewed 8 months ago

Rafael dos Santos Souza R. · Reviewed 8 months ago

Htut K. · Reviewed 8 months ago

Ahmed A. · Reviewed 8 months ago

ARTI M. · Reviewed 8 months ago

Gowtham K. · Reviewed 8 months ago

Giovanni K. · Reviewed 8 months 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 8 months 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 8 months ago

Juan Pablo I. · Reviewed 8 months ago

Vikyath P. · Reviewed 8 months ago

LUIZ T. · Reviewed 8 months ago

Oscar H. · Reviewed 8 months ago

Kalaiselvi S. · Reviewed 8 months ago

Niranjan U. · Reviewed 8 months ago

Amirlan S. · Reviewed 8 months ago

Jaime S. · Reviewed 8 months ago

Amirlan S. · Reviewed 8 months ago

Franklin C. · Reviewed 8 months ago

Marek Z. · Reviewed 8 months ago

Izzaldi I. · Reviewed 8 months ago

Diego G. · Reviewed 8 months 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 8 months ago