[
https://issues.apache.org/jira/browse/BEAM-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478379#comment-17478379
]
Israel Herraiz commented on BEAM-10905:
---------------------------------------
This was a "self bug" that I logged so I would not forget (<confession>and I
forgot about the JIRA issue... </confession>). I added the `withTempDataset`
option to BigQueryIO (as part of a customer requirement that needed to control
where the temporary data was being written to).
Using the project option in the pipeline options would work, but I added this
because I think that having the temp dataset in a different project could also
be useful for some customers.
I think I will now take the time to make the change :), and I will
add[~chamikara] as reviewer to the PR.
> 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)
