Serverless Data Processing with Dataflow - Writing an ETL Pipeline using Apache Beam and Dataflow (Python) Reviews

Rishabh S. · Reviewed about 1 year ago

Nobuo E. · Reviewed about 1 year ago

Adeepa N. · Reviewed about 1 year ago

Nihar Ranjan S. · Reviewed about 1 year ago

mindiya k. · Reviewed about 1 year ago

Oleksandr G. · Reviewed about 1 year ago

Rahul B. · Reviewed about 1 year ago

Arun S. · Reviewed about 1 year ago

zephyr z. · Reviewed about 1 year ago

Pasindu Sewmuthu A. · Reviewed about 1 year ago

Priyansh M. · Reviewed about 1 year ago

Jatin S. · Reviewed about 1 year ago

Franklin C. · Reviewed about 1 year ago

Febri A. · Reviewed about 1 year ago

Md F. · Reviewed about 1 year ago

Lucky W. · Reviewed about 1 year ago

Abhay M. · Reviewed about 1 year ago

Gustavo Kazuiti M. · Reviewed about 1 year ago

lohau l. · Reviewed about 1 year ago

achmad a. · Reviewed about 1 year ago

achmad a. · Reviewed about 1 year ago

Chew (. · Reviewed about 1 year ago

It seemed like there was some really good stuff in here, but the coding steps were a bit arbitrary/loosely connected. Maybe having a section somewhere that showed the data or the transform visually as well as what was expected to be written would have been nice. This was probably the first lab that made me really think about a Beam pipeline, but the contrast between filling code in and the drop-off to the Python code was large enough that I "felt" like I was doing something wrong. Maybe even marking the sections in the code as "Task 1 Goes Here" would have helped. This could be combined with a "What order does the pipeline definition, options, run, and then stages within run go" type of question to be very effective (for me).

Kyle S. · Reviewed about 1 year ago

HS R. · Reviewed about 1 year ago

Sameer K. · Reviewed about 1 year ago