Could not find BigQuery jobs in not US location

[m22r]

I'm trying to throw a query to BigQuery's dataset in asia-northeast1, but digdag can't find job's status.
It seem to be searching jobs with format ${PROJECT_NAME}:${JOB_ID} instead of ${PROJECT_NAME}:${LOCATION}:${JOB_ID}. isn't it?

error logs

2019-04-16 21:41:43 +0900 [ERROR] (0095@[0:dataFlow]+main+test) io.digdag.core.agent.OperatorManager: Task +main+test failed.
digdag_1       | 404 Not Found
digdag_1       | {
digdag_1       |   "code" : 404,
digdag_1       |   "errors" : [ {
digdag_1       |     "domain" : "global",
digdag_1       |     "message" : "Not found: Job my-gcp-project:digdag_s0_p_my-digdag-project_w_main_t_950_a_13_6aa3ad0c-ebd2-4f78-a6b7-0c3e47957436",
digdag_1       |     "reason" : "notFound"
digdag_1       |   } ],
digdag_1       |   "message" : "Not found: Job my-gcp-project:digdag_s0_p_my-digdag-project_w_main_t_950_a_13_6aa3ad0c-ebd2-4f78-a6b7-0c3e47957436",
digdag_1       |   "status" : "NOT_FOUND"
digdag_1       | } (google json response)

main.dig

test:
   bq>: queries/test.sql
   location: asia-northeast1
   dataset: my_dataset

queries/test.sql

SELECT
  *
FROM
  `my_dataset.my_table`

[yoyama]

@m22r Thanks for your report. Unfortunately I don't have GCP account to check your report. Please wait for a while.

[kosukekurimoto]

I have the same problem. Is this bug likely to be resolved?

[yoyama]

Sorry, I don't have time to handle this yet. But I think this should be solved.

[kosukekurimoto]

A temporary solution is possible by using the bq command.

+my_step:
  sh>: bq --location=asia-northeast1 query --project_id=${BIGQUERY_GCP_PROJECT} --batch --destination_table='${BIGQUERY_OPEN_DATASET}.${BIGQUERY_TABLE}' --replace=true --use_legacy_sql=false 'SELECT * FROM `${BIGQUERY_DATASET}.${BIGQUERY_TABLE}`'

[t-kazu]

When will this problem be resolved?
Do I need to use the bq command?

[hiroyuki-sato]

Hello, @t-kazu
AFAIK, Unfortunately, you still need to use bq command.

[toyama0919]

Hi.

location support not yet available?