Processamento de dados sem servidor com Dataflow: Monitoring, Logging e Error Reporting para jobs do Dataflow avaliações

Rock P. · Revisado há over 4 years

Sumbono S. · Revisado há over 4 years

shawn r. · Revisado há over 4 years

Jimmy L. · Revisado há over 4 years

Invalid BigQuery check failed

Duy H. · Revisado há over 4 years

Hello, There is an error somewhere in this lab . It is impossible to validate the second step where it is requested to click on the error link in the diognistic tab ( dataflow job log) and because of that I couldn't validate the Lab.

Oussama H. · Revisado há over 4 years

Abanob F. · Revisado há over 4 years

Progress check not working

Tsz Kin L. · Revisado há over 4 years

Gabriel A. · Revisado há over 4 years

Mashu S. · Revisado há over 4 years

David R. · Revisado há over 4 years

This lab is failing the third validation step.

Mario R. · Revisado há over 4 years

Onur B. · Revisado há over 4 years

Juliano L. · Revisado há over 4 years

broken monitor

Randi-Michelle C. · Revisado há over 4 years

Jimmy L. · Revisado há over 4 years

Task 3 does not seem to be completing successfully for me. The requirement is to simply open the link in the dataflow error message under the diagnostics tab. I believe this is not working because the intentional invalid name bugquery-public-data.crypto_bitcoin.transactions in the lab gives me the error “permission denied” instead of “dataset not found”.

Jeremy D. · Revisado há over 4 years

Jimmy L. · Revisado há over 4 years

Duggirala V. · Revisado há over 4 years

Vladimir U. · Revisado há over 4 years

Aymen N. · Revisado há over 4 years

Your lab is broken, it is not adding the points even after completing the tasks.

Yash G. · Revisado há over 4 years

doesn't work

Meng Oon L. · Revisado há over 4 years

This step does not update score in task "Invalid Bigquery table": "When you click on the Diagnostics tab, you will see a clickable link. Click on it and this takes you to the Error Reporting page. This shows us an expanded view of the error. Looking at the stack trace, you will see the issue: a typo in the pipeline code"

Antonio M. · Revisado há over 4 years

Antoni Vicent S. · Revisado há over 4 years