关于“Serverless Data Analysis with Dataflow: Side Inputs (Python)”的评价

41311 条评价

Walter W. · 已于 over 2 years前审核

Thamyaa A. · 已于 over 2 years前审核

Islam T. · 已于 over 2 years前审核

Xiao C. · 已于 over 2 years前审核

Shiva C. · 已于 over 2 years前审核

We keep getting this error, JavaProjectsThatNeedHelp.py:163: BeamDeprecationWarning: BigQuerySource is deprecated since 2.25.0. Use ReadFromBigQuery instead. bigqcollection = p | 'ReadFromBQ' >> beam.io.Read(beam.io.BigQuerySource(project=project,query=get_java_query)) /usr/local/lib/python3.9/dist-packages/apache_beam/io/gcp/bigquery.py:2485: BeamDeprecationWarning: options is deprecated since First stable release. References to <pipeline>.options will not be supported temp_location = pcoll.pipeline.options.view_as(

Waleed G. · 已于 over 2 years前审核

Jai C. · 已于 over 2 years前审核

Islam T. · 已于 over 2 years前审核

Tamas S. · 已于 over 2 years前审核

Andik A. · 已于 over 2 years前审核

Tamas S. · 已于 over 2 years前审核

Ashutosh D. · 已于 over 2 years前审核

Jagadeesh N. · 已于 over 2 years前审核

Matthieu C. · 已于 over 2 years前审核

Zana O. · 已于 over 2 years前审核

Allam V. · 已于 over 2 years前审核

Sudarsan S. · 已于 over 2 years前审核

Amine K. · 已于 over 2 years前审核

Ben S. · 已于 over 2 years前审核

OMKAR B. · 已于 over 2 years前审核

ok

Sovers S. · 已于 over 2 years前审核

gnanaarasan j. · 已于 over 2 years前审核

Executing the pipeline on the cloud (Task 4, step 4) often results in the pipeline failing due to a ZONE_RESOURCE_POOL_EXHAUSTED error, and the instructions don't account for this error. The error can (probably) be suppressed right away by changing the region/zone of the job (by editing JavaProjectsThatNeedHelp.py, the relevant parameter is `'--region=us-central1',` at around line 155, and if you want to specify the zone you can add another parameter beside it called `'--worker_zone=<zone>'` — the zone MUST BE contained within the specified region), but it seems like changing to any region beside `us-central1` prevents the lab from counting the objective as completed. Alternatively, you can just wait and try again another time. I really think this lab should check whether the pipeline has been successfully run regardless of region, because an unlucky learner could end up hitting the resource pool exhausted error several times in a row and potentially be locked out of the lab while trying to debug it. I ran the lab 3 times before succeeding in `us-central1`. It also seems like people in other regions are persistently having another type of error, `'us-central1' violates constraint 'constraints/gcp.resourceLocations'`. If the lab accounted for work being done in different regions (and included some guidance about these potential errors), both of these issues would be easy to resolve. There are loads of people reporting the same issues in the reviews for this lab, the Java version of the lab, the Coursera forums for a Coursera course using this lab, and there is a GitHub issue about this on the training-data-analyst repo.

Nicholas C. · 已于 over 2 years前审核

自分の進め方が悪かったのか、最後の[進行状況を確認]押しても完了できなかった GCSのバケットにはファイルが作成されており、ローカル・クラウドそれぞれで更新がかかっていた "error": { "code": 400, "message": "(5b4cea77a6d05a9d): 'us-central1' violates constraint 'constraints/gcp.resourceLocations' on the resource 'projects/qwiklabs-gcp-02-54459e55a7fd'.", "status": "FAILED_PRECONDITION"

Yuhei K. · 已于 over 2 years前审核

ayushi p. · 已于 over 2 years前审核

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