Building Batch Pipelines in Cloud Data Fusion Reviews

Jhonatan A. · Reviewed כמעט 3 שנים ago

Mauricio M. · Reviewed כמעט 3 שנים ago

Guilherme F. · Reviewed כמעט 3 שנים ago

José Ricardo P. · Reviewed כמעט 3 שנים ago

João V. · Reviewed כמעט 3 שנים ago

good hands on

Vaibhav R. · Reviewed כמעט 3 שנים ago

Jayasree C. · Reviewed כמעט 3 שנים ago

I followed the tutorial but it's deprecated

Guilherme F. · Reviewed כמעט 3 שנים ago

Bagyaraj J. · Reviewed כמעט 3 שנים ago

Emil C. · Reviewed כמעט 3 שנים ago

NICOLAS . M. · Reviewed כמעט 3 שנים ago

siuuu

Oscar Andres C. · Reviewed כמעט 3 שנים ago

Maria Alejandra M. · Reviewed כמעט 3 שנים ago

Eanna H. · Reviewed כמעט 3 שנים ago

裕史 吉. · Reviewed כמעט 3 שנים ago

LUCAS . P. · Reviewed כמעט 3 שנים ago

LUCAS . P. · Reviewed כמעט 3 שנים ago

Walter Mario E. · Reviewed כמעט 3 שנים ago

LUCIANO ALONSO B. · Reviewed כמעט 3 שנים ago

CRISTOPHER ALEJANDRO F. · Reviewed כמעט 3 שנים ago

MAICKOL . M. · Reviewed בערך 3 שנים ago

resource was not sufficiently created before beginning of lab. resource was unable to be created

Chris C. · Reviewed בערך 3 שנים ago

Nice lab :)

Marco V. · Reviewed בערך 3 שנים ago

I followed the steps but when I tried to run the pipeline showed me an error: PROVISION task failed in REQUESTING_CREATE state for program run program_run:default.ETL-batch-pipeline3.-SNAPSHOT.workflow.DataPipelineWorkflow.89f41ae8-fa74-11ed-b4a4-2e10fca8661d due to Dataproc operation failure: INVALID_ARGUMENT: User not authorized to act as service account '1050979227747-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 '1050979227747-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 '1050979227747-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..

Heidi Alicia C. · Reviewed בערך 3 שנים ago

NICOLAS CAMILO G. · Reviewed בערך 3 שנים ago