Créer des transformations et préparer des données avec Wrangler dans Cloud Data Fusion avis

Siân J. · Examiné il y a environ 3 ans

Mihai P. · Examiné il y a environ 3 ans

Ayushmaan Singh J. · Examiné il y a environ 3 ans

CHETNA D. · Examiné il y a environ 3 ans

sorry got really lost and haven't understood this at all.

Andrew W. · Examiné il y a environ 3 ans

RAVEENA SAI B. · Examiné il y a environ 3 ans

Sabrina G. · Examiné il y a environ 3 ans

Yash Y. · Examiné il y a environ 3 ans

Vinicius S. · Examiné il y a environ 3 ans

Esperanza L. · Examiné il y a environ 3 ans

Valentin F. · Examiné il y a environ 3 ans

Aditya K. · Examiné il y a environ 3 ans

Martin D. · Examiné il y a environ 3 ans

Eduardo M. · Examiné il y a environ 3 ans

janardhan reddy g. · Examiné il y a environ 3 ans

Juan Jose M. · Examiné il y a environ 3 ans

Henrique B. · Examiné il y a environ 3 ans

Alae B. · Examiné il y a environ 3 ans

Mihály K. · Examiné il y a environ 3 ans

Pawel K. · Examiné il y a environ 3 ans

Eldad B. · Examiné il y a environ 3 ans

Gourav G. · Examiné il y a environ 3 ans

NIRBHAY S. · Examiné il y a environ 3 ans

Sam J. · Examiné il y a environ 3 ans

1st Attempt: The Wrangler Node would not connect to the BigQuery node - even after doing everything correctly and seeing there were no errors in the Cloud Data Fusion Studio. This was really frustrating and the customer support team only suggested that I start all over again. 2nd Attempt: The nodes connected and there were no errors shown across all three nodes. However, the actual Run failed and did so three times. Error message: ERROR PROVISION task failed in REQUESTING_CREATE state for program run program_run:default.DemoBQ.-SNAPSHOT.workflow.DataPipelineWorkflow.1e8717a3-f2ac-11ed-abaf-f2872b601244 due to Dataproc operation failure: INVALID_ARGUMENT: User not authorized to act as service account '497045051724-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 '497045051724-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 '497045051724-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.. 3rd Attempt: Same steps but this time it worked.

Ricardo R. · Examiné il y a environ 3 ans