You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, etl_worker crashes in local development mode when a paris-traceroute archive is supplied as a URL.
Steps to reproduce:
Navigate to cmd/etl_worker within the ETL project.
Run go run ./etl_worker.go -service_port :8080 -output_dir ./output -output local.
Open up another terminal and set the URL variable to some paris-traceroute archive (e.g., URL=gs://archive-measurement-lab/paris-traceroute/2019/11/19/20191119T000000Z-mlab1-ord03-paris-traceroute-0000.tgz).
Run curl "http://localhost:8081/v2/worker?filename=$URL"
Ah, so there are currently two processing paths in the etl_worker: one for the "v1" system, and another for the "v2" system.
the "v1" path (/worker) is used by the v1 pipeline, web100 data types (and any others not yet migrated to v2).
the "v2" path (/v2/worker) is used by the v2 pipeline and ordinarily runs in the GKE environment. v2 does not yet support all data types. The "Traceroute migration" work is in part to solve this.
So, try the same GCS URL with the resource path /worker instead.
I tried with the /worker path. I think you're right about the v1 system not supporting local output, because now the output is this error: 2021/10/12 13:57:26 insert.go:299: InsertErr googleapi: Error 400: The destination table is invalid: projec_id , dataset_id base_tables, table_id: traceroute., invalid on traceroute_20191119
Currently,
etl_worker
crashes in local development mode when a paris-traceroute archive is supplied as a URL.Steps to reproduce:
go run ./etl_worker.go -service_port :8080 -output_dir ./output -output local
.URL=gs://archive-measurement-lab/paris-traceroute/2019/11/19/20191119T000000Z-mlab1-ord03-paris-traceroute-0000.tgz
).curl "http://localhost:8081/v2/worker?filename=$URL"
Note: this does not happen with other datatypes (e.g., PCAP, hopannotation1, scamper1).
The text was updated successfully, but these errors were encountered: