Building Dynamic Pipelines in Cloud Data Fusion Using Macros Reviews

Manisha K. · Reviewed over 2 years ago

Nancy L. · Reviewed over 2 years ago

Shreya N. · Reviewed over 2 years ago

Service Account : not given at details page(DataFusion)

Manoj K. · Reviewed over 2 years ago

Prakash S. · Reviewed over 2 years ago

1.Because maybe the lab is old, we need to create a service account named "cloud-datafusion-management-sa" and grant it the "Cloud Data Fusion API Service Agent" permission. This is only for 25 points. 2.By default, Data Fusion uses the ***compute@developer.gserviceaccount.com service account, which requires permissions such as "Cloud Data Fusion API Service Agent," "Cloud Data Fusion Runner," "Dataproc Worker," and "Editor." 3.Additionally, the user account student-****@qwiklabs.net needs the "Service Account User" permission. 4.Instead of using "titanic*.csv" as the filename, I used "*" to represent any characters in the filename. These are my observations. Cheers!

Mustafa K. · Reviewed over 2 years ago

Megan A. · Reviewed over 2 years ago

Vipul P. · Reviewed over 2 years ago

ok

Cesar Augusto B. · Reviewed almost 3 years ago

Hammad S. · Reviewed almost 3 years ago

Chai K. · Reviewed almost 3 years ago

Darren P. · Reviewed almost 3 years ago

Tawfiq C. · Reviewed almost 3 years ago

Arun K. · Reviewed almost 3 years ago

Natasha L. · Reviewed almost 3 years ago

Ashish K. · Reviewed almost 3 years ago

nice

Nick k. · Reviewed almost 3 years ago

Fabian A A. · Reviewed almost 3 years ago

Albin A. · Reviewed almost 3 years ago

Easwaramoorthy M. · Reviewed almost 3 years ago

Ankur J. · Reviewed almost 3 years ago

Sreenivasa H. · Reviewed almost 3 years ago

PREETHAM J. · Reviewed almost 3 years ago

Juhi N. · Reviewed almost 3 years ago

not working the service account have the roles indicated but when runing the pipeline PROVISION task failed in REQUESTING_CREATE state for program run program_run:default.Static-ETL.-SNAPSHOT.workflow.DataPipelineWorkflow.85777513-0a1a-11ee-86b9-86b1358a2a63 due to Dataproc operation failure: INVALID_ARGUMENT: User not authorized to act as service account '333683058265-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 '333683058265-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 '333683058265-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..

Angie M. · Reviewed almost 3 years ago