Serverless Data Processing with Dataflow - Writing an ETL Pipeline using Apache Beam and Dataflow (Python) avis
10459 avis
Nobuo E. · Examiné il y a 6 mois
Adeepa N. · Examiné il y a 6 mois
Nihar Ranjan S. · Examiné il y a 6 mois
mindiya k. · Examiné il y a 6 mois
Oleksandr G. · Examiné il y a 6 mois
Rahul B. · Examiné il y a 6 mois
Arun S. · Examiné il y a 6 mois
zephyr z. · Examiné il y a 6 mois
Pasindu Sewmuthu A. · Examiné il y a 6 mois
Priyansh M. · Examiné il y a 6 mois
Jatin S. · Examiné il y a 6 mois
Franklin C. · Examiné il y a 6 mois
Febri A. · Examiné il y a 6 mois
Md F. · Examiné il y a 6 mois
Lucky W. · Examiné il y a 6 mois
Abhay M. · Examiné il y a 6 mois
Gustavo Kazuiti M. · Examiné il y a 6 mois
lohau l. · Examiné il y a 6 mois
achmad a. · Examiné il y a 6 mois
achmad a. · Examiné il y a 6 mois
Chew (. · Examiné il y a 6 mois
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 6 mois
HS R. · Examiné il y a 6 mois
Sameer K. · Examiné il y a 6 mois
Jose David L. · Examiné il y a 6 mois
Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.