Processamento ETL no Google Cloud com o Dataflow e o BigQuery (Python) avaliações

Tony L. · Revisado há over 5 years

WORKERS WERE TOO SLOW

James S. · Revisado há over 5 years

Ervin W. · Revisado há over 5 years

Dillon B. · Revisado há 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. · Revisado há over 5 years

Kiril Y. · Revisado há over 5 years

Diego F. · Revisado há over 5 years

upendra t. · Revisado há over 5 years

Jeremy J. · Revisado há over 5 years

Nilesh B. · Revisado há over 5 years

Shantanu S. · Revisado há over 5 years

data process is slow

Yi W. · Revisado há over 5 years

Oğuzhan A. · Revisado há over 5 years

當間 祐. · Revisado há over 5 years

Shannon B. · Revisado há over 5 years

Gary B. · Revisado há over 5 years

Pierre H. · Revisado há over 5 years

Arduino C. · Revisado há over 5 years

Good

Oscar M. · Revisado há over 5 years

Oguz H. · Revisado 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. · Revisado há 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. · Revisado há over 5 years

Emanuela C. · Revisado há over 5 years

Zouhair J. · Revisado há over 5 years

Branislav N. · Revisado há over 5 years