Redacting Confidential Data within your Pipelines in Cloud Data Fusion Reviews

Quota exceeded for quota metric 'Number of requests' and limit 'Number of requests per minute' of service 'dlp.googleapis.com'

Nikka Z. · Reviewed about 2 hours ago

Evelyn Roxana F. · Reviewed about 21 hours ago

Chandra Prasad K. · Reviewed 1 day ago

Ravali B. · Reviewed 1 day ago

Karthik B. · Reviewed 3 days ago

Flavio K. · Reviewed 4 days ago

oktay k. · Reviewed 5 days ago

This labs needs a lot of attention. It cannot be completed in its current state if the instructions are followed. There are a myriad missing permissions, causing a lot of failures. The service account does not have access to the created bucket. The deployed pipeline does not have permissions to execute. The cloud shell editor does not include the step for binding the project, so the initial bucket creation will fail unless you know how to fix this already.

Leandre R. · Reviewed 14 days ago

Mahima J. · Reviewed 14 days ago

Satyakam M. · Reviewed 14 days ago

Vin M. · Reviewed 15 days ago

Flavio K. · Reviewed 15 days ago

Rakesh G. · Reviewed 20 days ago

Subham J. · Reviewed 20 days ago

Hao N. · Reviewed 20 days ago

Leena D. · Reviewed 21 days ago

Received below error PROVISION task failed in REQUESTING_CREATE state for program run program_run:default.Pipeline.b44acb33-7670-11ef-9f45-6e5445be3049.workflow.DataPipelineWorkflow.c031994a-7672-11ef-9237-6e5445be3049 due to Dataproc operation failure: INVALID_ARGUMENT: User not authorized to act as service account '88048993943-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 '88048993943-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 '88048993943-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..

Ninad K. · Reviewed 21 days ago

Cesar H. · Reviewed 23 days ago

Cesar H. · Reviewed 23 days ago

Balaji K. · Reviewed about 1 month ago

Kalyan Kumar M. · Reviewed about 1 month ago

Belal A. · Reviewed about 1 month ago

The last excersise didnt work, but was funny and interisting.

91201241 HECTOR RAFAEL V. · Reviewed about 1 month ago

Phanichand R. · Reviewed about 1 month ago

Peter F. · Reviewed about 1 month ago