关于“使用 Dataflow 和 BigQuery (Python) 在 Google Cloud 上进行 ETL 处理”的评价

Tony L. · 已于 over 5 years前审核

WORKERS WERE TOO SLOW

James S. · 已于 over 5 years前审核

Ervin W. · 已于 over 5 years前审核

Dillon B. · 已于 over 5 years前审核

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

Liran B. · 已于 over 5 years前审核

Kiril Y. · 已于 over 5 years前审核

Diego F. · 已于 over 5 years前审核

upendra t. · 已于 over 5 years前审核

Jeremy J. · 已于 over 5 years前审核

Nilesh B. · 已于 over 5 years前审核

Shantanu S. · 已于 over 5 years前审核

data process is slow

Yi W. · 已于 over 5 years前审核

Oğuzhan A. · 已于 over 5 years前审核

當間 祐. · 已于 over 5 years前审核

Shannon B. · 已于 over 5 years前审核

Gary B. · 已于 over 5 years前审核

Pierre H. · 已于 over 5 years前审核

Arduino C. · 已于 over 5 years前审核

Good

Oscar M. · 已于 over 5 years前审核

Oguz H. · 已于 over 5 years前审核

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. · 已于 over 5 years前审核

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. · 已于 over 5 years前审核

Emanuela C. · 已于 over 5 years前审核

Zouhair J. · 已于 over 5 years前审核

Branislav N. · 已于 over 5 years前审核