在 Google Cloud 上使用 Dataflow 和 BigQuery 處理 ETL 作業 (Python) Reviews

Tony L. · Reviewed over 5 years ago

WORKERS WERE TOO SLOW

James S. · Reviewed over 5 years ago

Ervin W. · Reviewed over 5 years ago

Dillon B. · Reviewed over 5 years ago

The time allotted is too short. The lab doesn't really explain what is going on and how to develop the modules.

Liran B. · Reviewed over 5 years ago

Kiril Y. · Reviewed over 5 years ago

Diego F. · Reviewed over 5 years ago

upendra t. · Reviewed over 5 years ago

Jeremy J. · Reviewed over 5 years ago

Nilesh B. · Reviewed over 5 years ago

Shantanu S. · Reviewed over 5 years ago

data process is slow

Yi W. · Reviewed over 5 years ago

Oğuzhan A. · Reviewed over 5 years ago

當間 祐. · Reviewed over 5 years ago

Shannon B. · Reviewed over 5 years ago

Gary B. · Reviewed over 5 years ago

Pierre H. · Reviewed over 5 years ago

Arduino C. · Reviewed over 5 years ago

Good

Oscar M. · Reviewed over 5 years ago

Oguz H. · Reviewed over 5 years ago

Not entirely clear what the Dataflow python scripts are doing. The combinations of pipe operators and >> in Python is not something I'm familiar with and could use a brief explanation

Nick S. · Reviewed over 5 years ago

The first apache beam pipeline is confusing because the code by default will output in the usa_names table instead of usa_names_transformed table as expected by the check. I had to specify manually the output parameter by modifying the command line call to data_ingestion.py. Some words explaining that we should specify ourselves the right destination would be good

Damien C. · Reviewed over 5 years ago

Emanuela C. · Reviewed over 5 years ago

Zouhair J. · Reviewed over 5 years ago

Branislav N. · Reviewed over 5 years ago