Cloud Data Fusion で Wrangler を使用してデータ変換を作成し、データを準備する のレビュー

Jones Siân · 約3年前にレビュー済み

Popa Mihai · 約3年前にレビュー済み

Jamwal Ayushmaan Singh · 約3年前にレビュー済み

DIWAKAR CHETNA · 約3年前にレビュー済み

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

WILCOX Andrew · 約3年前にレビュー済み

BEEREY RAVEENA SAI · 約3年前にレビュー済み

Geuna Sabrina · 約3年前にレビュー済み

Yadav Yash · 約3年前にレビュー済み

Starlino Vinicius · 約3年前にレビュー済み

Lizardo Esperanza · 約3年前にレビュー済み

Fera Valentin · 約3年前にレビュー済み

Kumar Aditya · 約3年前にレビュー済み

Dijkstra Martin · 約3年前にレビュー済み

Moreira Eduardo · 約3年前にレビュー済み

gaddampally janardhan reddy · 約3年前にレビュー済み

Morad Fernandez Juan Jose · 約3年前にレビュー済み

Bustamante Paganini Henrique · 約3年前にレビュー済み

Bohoudi Alae · 約3年前にレビュー済み

Koczman Mihály · 約3年前にレビュー済み

Krause Pawel · 約3年前にレビュー済み

Berkowitz Eldad · 約3年前にレビュー済み

Garg Gourav · 約3年前にレビュー済み

SHARMA NIRBHAY · 約3年前にレビュー済み

John Sam · 約3年前にレビュー済み

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.

Redd Ricardo · 約3年前にレビュー済み