Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Python SDK chain after WriteToBigQuery example is incorrect for file_loads method #31372

Closed
3 of 16 tasks
tangsiwei0831 opened this issue May 22, 2024 · 0 comments · Fixed by #31443
Closed
3 of 16 tasks

Comments

@tangsiwei0831
Copy link

What happened?

In

return (result.load_jobid_pairs, result.copy_jobid_pairs) | beam.Flatten()
, the documentation states that the chain operation for file loads is
return (result.load_jobid_pairs, result.copy_jobid_pairs) | beam.Flatten()

In fact, according to

destination_load_jobid_pairs=output[
and
destination_copy_jobid_pairs=output[
, it should be
return (result.destination_load_jobid_pairs, result.destination_copy_jobid_pairs) | beam.Flatten()

Issue Priority

Priority: 3 (minor)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
liferoad added a commit to liferoad/beam that referenced this issue May 29, 2024
@liferoad liferoad self-assigned this May 29, 2024
tvalentyn pushed a commit that referenced this issue May 30, 2024
* Update bigquery.py

fix #31372

* fix lint
@github-actions github-actions bot added this to the 2.57.0 Release milestone May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants