[jira] [Commented] (BEAM-10905) BigQueryIO withTempDataset assumes that it is running on Dataflow

["Kenneth Knowles (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478207#comment-17478207 ] 

Kenneth Knowles commented on BEAM-10905:
----------------------------------------

I believe the expectation is that if you are using any GCP product, you will set the {{project}} pipeline option. So it isn't a bug, exactly, but could use clearer documentation. But I do think that directly supporting a fully qualified name makes sense. I may be missing something though, so I am pinging [~chamikara] who would be the best person to consider it.

> BigQueryIO withTempDataset assumes that it is running on Dataflow
> -----------------------------------------------------------------
>
>                 Key: BEAM-10905
>                 URL: https://issues.apache.org/jira/browse/BEAM-10905
>             Project: Beam
>          Issue Type: New Feature
>          Components: extensions-java-gcp
>    Affects Versions: 2.23.0
>            Reporter: Israel Herraiz
>            Priority: P2
>              Labels: Clarified, bigquery
>
> The option {{withTempDataset}} of BigQueryIO only asks for a dataset name, assumes that the pipeline is running on Dataflow in a GCP project and uses that project to create the temp dataset.
> This option should accept a fully qualified dataset (project + dataset) instead.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)