关于“Serverless Data Processing with Dataflow - Writing an ETL Pipeline using Apache Beam and Dataflow (Python)”的评价

Konstantin O. · 已于 about 1 year前审核

Rishabh S. · 已于 about 1 year前审核

Nobuo E. · 已于 about 1 year前审核

Adeepa N. · 已于 about 1 year前审核

Nihar Ranjan S. · 已于 about 1 year前审核

mindiya k. · 已于 about 1 year前审核

Oleksandr G. · 已于 about 1 year前审核

Rahul B. · 已于 about 1 year前审核

Arun S. · 已于 about 1 year前审核

zephyr z. · 已于 about 1 year前审核

Pasindu Sewmuthu A. · 已于 about 1 year前审核

Priyansh M. · 已于 about 1 year前审核

Jatin S. · 已于 about 1 year前审核

Franklin C. · 已于 about 1 year前审核

Febri A. · 已于 about 1 year前审核

Md F. · 已于 about 1 year前审核

Lucky W. · 已于 about 1 year前审核

Abhay M. · 已于 about 1 year前审核

Gustavo Kazuiti M. · 已于 about 1 year前审核

lohau l. · 已于 about 1 year前审核

achmad a. · 已于 about 1 year前审核

achmad a. · 已于 about 1 year前审核

Chew (. · 已于 about 1 year前审核

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. · 已于 about 1 year前审核

HS R. · 已于 about 1 year前审核