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

Nihar Ranjan S. · Examiné il y a plus d'un an

mindiya k. · Examiné il y a plus d'un an

Oleksandr G. · Examiné il y a plus d'un an

Rahul B. · Examiné il y a plus d'un an

Arun S. · Examiné il y a plus d'un an

zephyr z. · Examiné il y a plus d'un an

Pasindu Sewmuthu A. · Examiné il y a plus d'un an

Priyansh M. · Examiné il y a plus d'un an

Jatin S. · Examiné il y a plus d'un an

Franklin C. · Examiné il y a plus d'un an

Febri A. · Examiné il y a plus d'un an

Md F. · Examiné il y a plus d'un an

Lucky W. · Examiné il y a plus d'un an

Abhay M. · Examiné il y a plus d'un an

Gustavo Kazuiti M. · Examiné il y a plus d'un an

lohau l. · Examiné il y a plus d'un an

achmad a. · Examiné il y a plus d'un an

achmad a. · Examiné il y a plus d'un an

Chew (. · Examiné il y a plus d'un an

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. · Examiné il y a plus d'un an

HS R. · Examiné il y a plus d'un an

Sameer K. · Examiné il y a plus d'un an

Jose David L. · Examiné il y a plus d'un an

Nishita K. · Examiné il y a plus d'un an

Sumit S. · Examiné il y a plus d'un an