关于“Building Batch Pipelines in Cloud Data Fusion”的评价
正在加载…
未找到任何结果。

    关于“Building Batch Pipelines in Cloud Data Fusion”的评价

    3810 条评价

    not well will do tomorrow

    Suganya R. · 已于 about 1 year前审核

    Satish G. · 已于 about 1 year前审核

    Sesha Venkata Sriram E. · 已于 about 1 year前审核

    Jordan V. · 已于 about 1 year前审核

    Rahul P. · 已于 about 1 year前审核

    守男 毛. · 已于 about 1 year前审核

    Anjaneyulu B. · 已于 about 1 year前审核

    Chinthamreddy D. · 已于 about 1 year前审核

    claire q. · 已于 about 1 year前审核

    Chinthamreddy D. · 已于 about 1 year前审核

    Angelo P. · 已于 about 1 year前审核

    Chinthamreddy D. · 已于 about 1 year前审核

    Mari S. · 已于 about 1 year前审核

    Abhijit K. · 已于 about 1 year前审核

    Achmad Alfansyah N. · 已于 about 1 year前审核

    Abhishek S. · 已于 about 1 year前审核

    Pradeep N. · 已于 about 1 year前审核

    Sarbjit G. · 已于 about 1 year前审核

    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. · 已于 about 1 year前审核

    Henry C. · 已于 about 1 year前审核

    Steven W. · 已于 about 1 year前审核

    Harshdeep Singh P. · 已于 about 1 year前审核

    Maran A. · 已于 about 1 year前审核

    Chris D. · 已于 about 1 year前审核

    Yu Y. · 已于 about 1 year前审核

    我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。