리뷰 Dataflow와 BigQuery를 사용하여 Google Cloud에서 ETL 처리하기(Python)개
리뷰 80300개
Aditya k. · 5년 초과 전에 리뷰됨
Yue X. · 5년 초과 전에 리뷰됨
Ebin P. · 5년 초과 전에 리뷰됨
Jacky L. · 5년 초과 전에 리뷰됨
Chanyoung Park 박. · 5년 초과 전에 리뷰됨
佳代子 竹. · 5년 초과 전에 리뷰됨
Sri Harsha P. · 5년 초과 전에 리뷰됨
Muntakimur R. · 5년 초과 전에 리뷰됨
David Leonardo D. · 5년 초과 전에 리뷰됨
Again ran this lab and follow all the instruction. Checked all the permissions are in place but still dataflow job failed with below error: Workflow failed. Causes: There was a problem refreshing your credentials. Please check: 1. Dataflow API is enabled for your project. 2. Make sure both the Dataflow service account and the controller service account have sufficient permissions. If you are not specifying a controller service account, ensure the default Compute Engine service account [PROJECT_NUMBER]-compute@developer.gserviceaccount.com exists and has sufficient permissions. If you have deleted the default Com pute Engine service account, you must specify a controller service account. For more information, see: https://cloud.google.com/dataflow/docs/concepts/security-and-permissio ns#security_and_permissions_for_pipelines_on_google_cloud_platform. , There is no cloudservices robot account for your project. Please ensure that the Dataflow API is enabl ed for your project.
Rakesh C. · 5년 초과 전에 리뷰됨
Yi M. · 5년 초과 전에 리뷰됨
Chirag S. · 5년 초과 전에 리뷰됨
Krithika M. · 5년 초과 전에 리뷰됨
Miguel G. · 5년 초과 전에 리뷰됨
Again ran this lab and follow all the instruction. Checked all the permissions are in place but still dataflow job failed with below error: Workflow failed. Causes: There was a problem refreshing your credentials. Please check: 1. Dataflow API is enabled for your project. 2. Make sure both the Dataflow service account and the controller service account have sufficient permissions. If you are not specifying a controller service account, ensure the default Compute Engine service account [PROJECT_NUMBER]-compute@developer.gserviceaccount.com exists and has sufficient permissions. If you have deleted the default Com pute Engine service account, you must specify a controller service account. For more information, see: https://cloud.google.com/dataflow/docs/concepts/security-and-permissio ns#security_and_permissions_for_pipelines_on_google_cloud_platform. , There is no cloudservices robot account for your project. Please ensure that the Dataflow API is enabl ed for your project.
Rakesh C. · 5년 초과 전에 리뷰됨
Follow lab steps but getting below error while running first dataflow job: python dataflow_python_examples/data_ingestion.py --project=$PROJECT --region=us-central1 --runner=DataflowRunner --staging_location=gs://$PROJECT/test --temp_location gs://$PROJECT/test --input gs://$PROJECT/data_files/head_usa_names.csv --save_main_session Workflow failed. Causes: There was a problem refreshing your credentials. Please check: 1. Dataflow API is enabled for your project. 2. Make sure both the Dataflow service account and the controller service account have sufficient permissions. If you are not specifying a controller service account, ensure the default Compute Engine service account [PROJECT_NUMBER]-compute@developer.gserviceaccount.com exists and has sufficient permissions. If you have deleted the default Compute Engine service account, you must specify a controller service account. For more information, see: https://cloud.google.com/dataflow/docs/concepts/security-and-permissions#security_and_permissions_for_pipelines_on_google_cloud_platform. , There is no cloudservices robot account for your project. Please ensure that the Dataflow API is enabled for your project.
Rakesh C. · 5년 초과 전에 리뷰됨
Anita Q. · 5년 초과 전에 리뷰됨
Steve M. · 5년 초과 전에 리뷰됨
Very nicely setup lab.. Thank you
Prakash S. · 5년 초과 전에 리뷰됨
tomoomi I. · 5년 초과 전에 리뷰됨
Ruchir J. · 5년 초과 전에 리뷰됨
shaik s. · 5년 초과 전에 리뷰됨
Y M. · 5년 초과 전에 리뷰됨
I had to add the following permissions on compute engine service account for this to work: Dataflow Admin Cloud Dataflow Service Agent Editor
Sarma P. · 5년 초과 전에 리뷰됨
J T. · 5년 초과 전에 리뷰됨
Google은 게시된 리뷰가 제품을 구매 또는 사용한 소비자에 의해 작성되었음을 보증하지 않습니다. 리뷰는 Google의 인증을 거치지 않습니다.