Opinie (Serverless Data Processing with Dataflow - Writing an ETL Pipeline using Apache Beam and Dataflow (Python))
11472 opinie
1. There are 2 issues running the lab: - lab 1: apache_beam.io.filesystem.BeamIOError: Match operation failed with exceptions {'gs://qwiklabs-gcp-04-9d1f7241cd59/events.json': RefreshError(TransportError("Failed to retrieve https://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/?recursive=true from the Google Compute Engine metadata service. Compute Engine Metadata server unavailable. Last exception: HTTPSConnectionPool(host='metadata.google.internal', port=443): Max retries exceeded with url: /computeMetadata/v1/instance/service-accounts/default/?recursive=true (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate - lab 2 Startup of the worker pool in us-central1 failed to bring up any of the desired 1 workers P.S. Not working http.client transport only supports the http scheme, httpswas specified P.S.S. export GCE_METADATA_MTLS_MODE=none resolves an issue with certificate. But still insufficient resources to run the job.
Igor P. · Sprawdzono 12 dni temu
1. There are 2 issues running the lab: - lab 1: apache_beam.io.filesystem.BeamIOError: Match operation failed with exceptions {'gs://qwiklabs-gcp-04-9d1f7241cd59/events.json': RefreshError(TransportError("Failed to retrieve https://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/?recursive=true from the Google Compute Engine metadata service. Compute Engine Metadata server unavailable. Last exception: HTTPSConnectionPool(host='metadata.google.internal', port=443): Max retries exceeded with url: /computeMetadata/v1/instance/service-accounts/default/?recursive=true (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate - lab 2 Startup of the worker pool in us-central1 failed to bring up any of the desired 1 workers P.S. Not working http.client transport only supports the http scheme, httpswas specified
Igor P. · Sprawdzono 13 dni temu
Luis Antonio C. · Sprawdzono 13 dni temu
Charles F. · Sprawdzono 13 dni temu
Too much confuse the Python file and Instructions were not clear to proceed and modify the files. The code is running with errors. Need support.
Venkateswarlu Kuriseti N. · Sprawdzono 13 dni temu
konda l. · Sprawdzono 14 dni temu
Jorge Alberto M. · Sprawdzono 16 dni temu
There is currently an issue with google.auth library (https://github.com/googleapis/google-cloud-python/issues/16090) that prevents me from finishing the lab - took a long time to find the root couse and I run out of time. Additionally, the worker zones and machine types have to be specified because without them the dataflow cannot spawn workers and jobs keep failing.
Przemyslaw S. · Sprawdzono 16 dni temu
1. There are 2 issues running the lab: - lab 1: apache_beam.io.filesystem.BeamIOError: Match operation failed with exceptions {'gs://qwiklabs-gcp-04-9d1f7241cd59/events.json': RefreshError(TransportError("Failed to retrieve https://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/?recursive=true from the Google Compute Engine metadata service. Compute Engine Metadata server unavailable. Last exception: HTTPSConnectionPool(host='metadata.google.internal', port=443): Max retries exceeded with url: /computeMetadata/v1/instance/service-accounts/default/?recursive=true (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate - lab 2 Startup of the worker pool in us-central1 failed to bring up any of the desired 1 workers
Igor P. · Sprawdzono 16 dni temu
Bartłomiej B. · Sprawdzono 16 dni temu
Alice Wu 吳馨妤 E. · Sprawdzono 19 dni temu
not enough recources to complete the lab
Stef v. · Sprawdzono 19 dni temu
Sriyansh S. · Sprawdzono 19 dni temu
Shaik S. · Sprawdzono 20 dni temu
Too abstract
Anirban S. · Sprawdzono 21 dni temu
EMIL-CRISTIAN C. · Sprawdzono 21 dni temu
Ram krishna Reddy S. · Sprawdzono 22 dni temu
Anatolii L. · Sprawdzono 22 dni temu
Ram krishna Reddy S. · Sprawdzono 23 dni temu
Ram krishna Reddy S. · Sprawdzono 23 dni temu
Ram krishna Reddy S. · Sprawdzono 23 dni temu
don't have enough resources to create pipeline
Anatolii L. · Sprawdzono 23 dni temu
Ram krishna Reddy S. · Sprawdzono 23 dni temu
Again, resources exhausted. THIS IS IMPOSSIBLE!!!!
Alejandro C. · Sprawdzono 24 dni temu
just did not work, the workers for dataflow where not working as expected
Christian . · Sprawdzono 24 dni temu
Nie gwarantujemy, że publikowane opinie pochodzą od konsumentów, którzy dane produkty kupili lub ich używali. Google nie weryfikuje opinii.