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

Joshua W. · Recensione inserita quasi 7 anni fa

Joshua W. · Recensione inserita quasi 7 anni fa

Kunal L. · Recensione inserita quasi 7 anni fa

Joshua W. · Recensione inserita quasi 7 anni fa

Steve T. · Recensione inserita quasi 7 anni fa

Bernd S. · Recensione inserita quasi 7 anni fa

Michael I. · Recensione inserita quasi 7 anni fa

Mark C. · Recensione inserita quasi 7 anni fa

Alexandre M. · Recensione inserita quasi 7 anni fa

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. · Recensione inserita quasi 7 anni fa

Oren L. · Recensione inserita quasi 7 anni fa

Ekta R. · Recensione inserita quasi 7 anni fa

Richard C. · Recensione inserita quasi 7 anni fa

Google Cloud Shell not working.

Narendra Babu O. · Recensione inserita quasi 7 anni fa

嘉瑋 姚. · Recensione inserita quasi 7 anni fa

good

Pooja T. · Recensione inserita quasi 7 anni fa

Xiangyang S. · Recensione inserita quasi 7 anni fa

Muhammad F. · Recensione inserita quasi 7 anni fa

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. · Recensione inserita quasi 7 anni fa

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. · Recensione inserita quasi 7 anni fa

Benjamin R. · Recensione inserita quasi 7 anni fa

Debanjan D. · Recensione inserita quasi 7 anni fa

Balaji C. · Recensione inserita quasi 7 anni fa

Matthew W. · Recensione inserita quasi 7 anni fa

Anil Sagar R. · Recensione inserita quasi 7 anni fa