Análise de dados sem servidor com o Dataflow: entradas secundárias (Python) avaliações

Giorgio C. · Revisado há about 6 years

Marcus P. · Revisado há about 6 years

Lucas S. · Revisado há about 6 years

the execution of the job took a little longer then initially stated and I almost thought it was hanging

Madelaine D. · Revisado há about 6 years

Please provide answers to Task 3

Alice M. · Revisado há about 6 years

Alena S. · Revisado há about 6 years

Ayyappan P. · Revisado há about 6 years

Bhavana S. · Revisado há about 6 years

Rex W. · Revisado há about 6 years

Jerome A. · Revisado há about 6 years

João C. · Revisado há about 6 years

muy bueno

armando y. · Revisado há about 6 years

gustavo r. · Revisado há about 6 years

Jeya Prakash M. · Revisado há about 6 years

Jeya Prakash M. · Revisado há about 6 years

Weronika A. · Revisado há about 6 years

Sun H. · Revisado há about 6 years

Christian B. · Revisado há about 6 years

Calvin C. · Revisado há about 6 years

Jose Gilberto c. · Revisado há about 6 years

Juliano d. · Revisado há about 6 years

This entire lab is dependent on naming your bucket with the project name. Not only have different labs NOT done this, it's somewhat misleading and unrealistic (why would I name buckets with the project name) - also we later define what the bucket name is as $BUCKET, so it's extra useless!!! I reached the end of the lab only to realize that this was wrong, however I had already run the last script which spun up a dataflow job, which I needed to then stop from running so I could then run the script again against the correct bucket (with the project name). I know this is a bit nitpicky and was a result of ME not reading the directions closely enough. Perhaps make this direction bold so it is not missed.

Brad K. · Revisado há about 6 years

Lin-Ying C. · Revisado há about 6 years

Weronika A. · Revisado há about 6 years

Anjul S. · Revisado há about 6 years