Building Realtime Pipelines in Cloud Data Fusion Reviews

Vladimir S. · Reviewed over 1 year ago

Ramdas J. · Reviewed over 1 year ago

Super confusing instructions on "enabling" dataflow. You have to disable then reenable to "enable" it... weird and confusing. Not really explained why early on.

Ryan D. · Reviewed over 1 year ago

Nikhil K. · Reviewed over 1 year ago

Sebastian S. · Reviewed over 1 year ago

Mabel O. · Reviewed over 1 year ago

Ashok K. · Reviewed over 1 year ago

Janaki Devi G. · Reviewed over 1 year ago

Saurabh S. · Reviewed over 1 year ago

Anudeep C. · Reviewed over 1 year ago

lipsa p. · Reviewed over 1 year ago

ABHISHEK M. · Reviewed over 1 year ago

Fallas en el proceso, no indica bien un correo

Laura Camila M. · Reviewed over 1 year ago

Omar Giovanny B. · Reviewed over 1 year ago

Yery Agusto P. · Reviewed over 1 year ago

Miguel Alejandro G. · Reviewed over 1 year ago

Arvind S. · Reviewed over 1 year ago

Jeremy T. · Reviewed over 1 year ago

Gabby T. · Reviewed over 1 year ago

Gabby T. · Reviewed over 1 year ago

Mevlut B. · Reviewed over 1 year ago

sagar m. · Reviewed over 1 year ago

On ne peut pas finaliser le lab : il manque en source de donnée pub/sub

Bruno B. · Reviewed over 1 year ago

Jakub G. · Reviewed over 1 year ago

"ERROR PROVISION task failed in REQUESTING_CREATE state for program run program_run:default.Realtime_Pipeline_v1.-SNAPSHOT.spark.DataStreamsSparkStreaming.b833aa6d-d161-11ed-a5f5-8669903c498d due to Dataproc operation failure: INVALID_ARGUMENT: User not authorized to act as service account '299062934110-compute@developer.gserviceaccount.com'. To act as a service account, user must have one of [Owner, Editor, Service Account Actor] roles. See https://cloud.google.com/iam/docs/understanding-service-accounts for additional details. For troubleshooting Dataproc errors, refer to https://cloud.google.com/dataproc/docs/troubleshooting Caused by: io.grpc.StatusRuntimeException: INVALID_ARGUMENT: User not authorized to act as service account '299062934110-compute@developer.gserviceaccount.com'. To act as a service account, user must have one of [Owner, Editor, Service Account Actor] roles. See https://cloud.google.com/iam/docs/understanding-service-accounts for additional details. Caused by: INVALID_ARGUMENT: User not authorized to act as service account '299062934110-compute@developer.gserviceaccount.com'. To act as a service account, user must have one of [Owner, Editor, Service Account Actor] roles. See https://cloud.google.com/iam/docs/understanding-service-accounts for additional details.."

Олександр З. · Reviewed over 1 year ago