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

Most of the time in this lab was spent waiting for worker teardown.

Alasdair C. · Reviewed over 7 years ago

Lots of extra reading of lots of similar code and not much learning due to similar commands. Due to the time it takes for each job to run, it is very easy to run out of time, especially if reading the code before running the jobs, which the lab suggests. I would recommend suggesting to read the code while the job is running to not waste time sitting and doing nothing while waiting for the jobs to finish.

Jack D. · Reviewed over 7 years ago

Amos Z. · Reviewed over 7 years ago

Rita L. · Reviewed over 7 years ago

The steps could be related to a specific scenario to illustrate.

Gabriel T. · Reviewed over 7 years ago

Kassia Helena O. · Reviewed over 7 years ago

Amos Z. · Reviewed over 7 years ago

Rafael P. · Reviewed over 7 years ago

Talles Henrique D. · Reviewed over 7 years ago

Tiago H. · Reviewed over 7 years ago

Show

Guilherme P. · Reviewed over 7 years ago

The content is awesome. The estimated time for delivery is not enough to harness all the content

Ricardo G. · Reviewed over 7 years ago

Jarvis T. · Reviewed over 7 years ago

Jose Luis G. · Reviewed over 7 years ago

RAFAEL G. · Reviewed over 7 years ago

Sijie S. · Reviewed over 7 years ago

Jose Luis G. · Reviewed over 7 years ago

Bernardo C. · Reviewed over 7 years ago

Anton R. · Reviewed over 7 years ago

Eshwar R. · Reviewed over 7 years ago

none

Nicolas P. · Reviewed over 7 years ago

Son V. · Reviewed over 7 years ago

I had to executed some instructions one by one, although the instructions doesn't indicate it, so I lose time to understand it

Gabriela R. · Reviewed over 7 years ago

Jackreece E. · Reviewed over 7 years ago

I'd much like an introductory paragraph for each task on what we're doing to which data. Currently, we're just following instructions without knowing the why or what.

Kevin K. · Reviewed over 7 years ago