Pemrosesan ETL di Google Cloud Menggunakan Dataflow dan BigQuery (Python) Ulasan

Joshua W. · Diulas hampir 7 tahun lalu

Kunal L. · Diulas hampir 7 tahun lalu

Joshua W. · Diulas hampir 7 tahun lalu

Steve T. · Diulas hampir 7 tahun lalu

Bernd S. · Diulas hampir 7 tahun lalu

Michael I. · Diulas hampir 7 tahun lalu

Mark C. · Diulas hampir 7 tahun lalu

Alexandre M. · Diulas hampir 7 tahun lalu

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. · Diulas hampir 7 tahun lalu

Oren L. · Diulas hampir 7 tahun lalu

Ekta R. · Diulas hampir 7 tahun lalu

Richard C. · Diulas hampir 7 tahun lalu

Google Cloud Shell not working.

Narendra Babu O. · Diulas hampir 7 tahun lalu

嘉瑋 姚. · Diulas hampir 7 tahun lalu

good

Pooja T. · Diulas hampir 7 tahun lalu

Xiangyang S. · Diulas hampir 7 tahun lalu

Muhammad F. · Diulas hampir 7 tahun lalu

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. · Diulas hampir 7 tahun lalu

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. · Diulas hampir 7 tahun lalu

Benjamin R. · Diulas hampir 7 tahun lalu

Debanjan D. · Diulas hampir 7 tahun lalu

Balaji C. · Diulas hampir 7 tahun lalu

Matthew W. · Diulas hampir 7 tahun lalu

Anil Sagar R. · Diulas hampir 7 tahun lalu

Rendson F. · Diulas hampir 7 tahun lalu