Closed ghost closed 5 years ago
zones are just not supported, feel free to send a pr in though 👍
@zwennesm I'm having the same problem and it seems that the library didn't add the europe-north1
string to the job's name when it's trying to locate it.
I'm currently trying to load tables into BigQuery and the job was able to run but I received the same error message due to the job name being different from those that is actually being run in BigQuery.
Whenever I'm trying to load a table from BigQuery the same error also shows as the library is not able to create a job to load the staging table from BigQuery to GCS. I was able to mitigate this load problem by using sqlContext.bigQueryTable("project_id:dataset.table")
instead.
Martijn, If you were able to find a workaround on your problem, I hope you'll be able to share it as well.
I started out with the same fix as you mentioned, but I ended up moving to the Spotify library due to issues with regions and running the application in Google Dataproc.
When you set the zone to the following value:
europe-north1
i get the error as listed below. Is this a bug or are zones just not supported (yet)?