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

Kunal L. · Reviewed almost 7 years ago

Joshua W. · Reviewed almost 7 years ago

Steve T. · Reviewed almost 7 years ago

Bernd S. · Reviewed almost 7 years ago

Michael I. · Reviewed almost 7 years ago

Mark C. · Reviewed almost 7 years ago

Alexandre M. · Reviewed almost 7 years ago

shit lab. full of bugs. did it 3 times and cant ever complete. slow spinning up and down of workers. atrocious. and such limited time. and there is issue recognising tasks i have already completed.

Decki K. · Reviewed almost 7 years ago

Oren L. · Reviewed almost 7 years ago

Ekta R. · Reviewed almost 7 years ago

Richard C. · Reviewed almost 7 years ago

Google Cloud Shell not working.

Narendra Babu O. · Reviewed almost 7 years ago

嘉瑋 姚. · Reviewed almost 7 years ago

good

Pooja T. · Reviewed almost 7 years ago

Xiangyang S. · Reviewed almost 7 years ago

Muhammad F. · Reviewed almost 7 years ago

This lab throws around terminology via the python script names like transformation, enrichment, and mart, but really things like transformation and enrichment would be separate steps from ingestion and not combined into one step. Also, some of the documentation in the lab is erroneous. For example in Step 6, it says in the step you will "Ingest the files from GCS" but that is not true -- Steps 6 uses data only from BigQuery and not from GCS. Furthermore, when you look at the resulting data from the last step, the process has replaced things like City with the customer name, so the example code is flawed. Finally, there is no architecture or data flow diagram -- no visual representation of what is going on; and also no mention of what Apache Beam is and how it relates to DataFlow. Finally, ETL is an outdated legacy term. Big Data uses other concepts and follows a different model than ETL.

Luther M. · Reviewed almost 7 years ago

Lab worked but some of the steps take an incredible amount of time if you sit and wait for them to complete on the CLI. Also "read the code" isn't a great explanation of each step. Each step feels like it was simply cut/pasted 5 times.

Jamal M. · Reviewed almost 7 years ago

Benjamin R. · Reviewed almost 7 years ago

Debanjan D. · Reviewed almost 7 years ago

Balaji C. · Reviewed almost 7 years ago

Matthew W. · Reviewed almost 7 years ago

Anil Sagar R. · Reviewed almost 7 years ago

Rendson F. · Reviewed almost 7 years ago

Vik M. · Reviewed almost 7 years ago