Opiniones sobre Crea canalizaciones por lotes en Cloud Data Fusion

Building Batch Pipelines in Cloud Data Fusion failure conditions and handling does not match: https://screenshot.googleplex.com/wJzqLoTK3NyAvex file:///home/cjac/Pictures/Screenshots/Screenshot%20from%202023-09-01%2016-05-39.png Preview succeeds Wrangler preview looks right exported pipeline json deleted original created new and imported failed. Duration: 3s Warnings: 0 Errors: 0 file:///home/cjac/Pictures/Screenshots/Screenshot%20from%202023-09-01%2016-20-20.png no log available. file:///home/cjac/Pictures/Screenshots/Screenshot%20from%202023-09-01%2016-21-14.png Deleted reloaded JSON reviewed screenshots closely The drop statement in teh screenshot says "drop body" and the example text provided suggests using "drop :body" I've removed the : before body Still fails no logs. I found an "Advanced logs" button. Here are those logs: 09/01/2023 16:27:55 INFO Creating Dataproc cluster cdap-etl-batch-2c957438-491f-11ee-92f2-7a38d82486cf in project qwiklabs-gcp-04-d3641979a841, in region us-east1, with image 2.0, with labels {goog-datafusion-version=6_8, cdap-version=6_8_3-1685052397284, goog-datafusion-edition=basic}, endpoint dataproc.googleapis.com:443 09/01/2023 16:27:56 ERROR PROVISION task failed in REQUESTING_CREATE state for program run program_run:default.ETL-batch-pipeline.-SNAPSHOT.workflow.DataPipelineWorkflow.2c957438-491f-11ee-92f2-7a38d82486cf due to Dataproc operation failure: INVALID_ARGUMENT: User not authorized to act as service account '221115439752-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 '221115439752-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 '221115439752-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.. According to this error, user must have Owner, Editor or Service Account Actor. There is no Service Account Actor available in the roles It currently has Cloud Data Fusion API Service Agent, Editor and Service Account User I added Owner. It is now Provisioning instead of failing It still fails. 09/01/2023 16:33:11 INFO Creating Dataproc cluster cdap-etl-batch-e8e13079-491f-11ee-8356-7a38d82486cf in project qwiklabs-gcp-04-d3641979a841, in region us-east1, with image 2.0, with labels {goog-datafusion-version=6_8, cdap-version=6_8_3-1685052397284, goog-datafusion-edition=basic}, endpoint dataproc.googleapis.com:443 09/01/2023 16:33:13 ERROR PROVISION task failed in REQUESTING_CREATE state for program run program_run:default.ETL-batch-pipeline.-SNAPSHOT.workflow.DataPipelineWorkflow.e8e13079-491f-11ee-8356-7a38d82486cf due to Dataproc operation failure: INVALID_ARGUMENT: User not authorized to act as service account '221115439752-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 '221115439752-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 '221115439752-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.. Perhaps it just needs some time for the ACLs to settle. file:///home/cjac/Pictures/Screenshots/Screenshot%20from%202023-09-01%2016-34-50.png missed the Grant service account user permission section.

C.J. C. · Se revisó hace alrededor de 2 años

Henry C. · Se revisó hace alrededor de 2 años

Steven W. · Se revisó hace alrededor de 2 años

Harshdeep Singh P. · Se revisó hace alrededor de 2 años

Maran A. · Se revisó hace alrededor de 2 años

Chris D. · Se revisó hace alrededor de 2 años

Yu Y. · Se revisó hace alrededor de 2 años

Sujana R. · Se revisó hace más de 2 años

AMATINTHALA B. · Se revisó hace más de 2 años

Awesome

Drishya G. · Se revisó hace más de 2 años

Shubham R. · Se revisó hace más de 2 años

Tracy B. · Se revisó hace más de 2 años

Would like additional explanations for why certain steps are necessary.

Anthony M. · Se revisó hace más de 2 años

Andrei I. · Se revisó hace más de 2 años

Scott B. · Se revisó hace más de 2 años

Francisca M. · Se revisó hace más de 2 años

Paul R. · Se revisó hace más de 2 años

Paul R. · Se revisó hace más de 2 años

Dotun O. · Se revisó hace más de 2 años

Priyanka S. · Se revisó hace más de 2 años

Tapan H. · Se revisó hace más de 2 años

Tapan H. · Se revisó hace más de 2 años

Dairon Danilo D. · Se revisó hace más de 2 años

Kiran B. · Se revisó hace más de 2 años

Tapan H. · Se revisó hace más de 2 años