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

[Epic]: Ensure all exception blocks in Tier 1 Beam IOs are safe #28080

Closed
3 of 15 tasks
damondouglas opened this issue Aug 21, 2023 · 2 comments
Closed
3 of 15 tasks

[Epic]: Ensure all exception blocks in Tier 1 Beam IOs are safe #28080

damondouglas opened this issue Aug 21, 2023 · 2 comments

Comments

@damondouglas
Copy link
Contributor

damondouglas commented Aug 21, 2023

What needs to happen?

This issue serves as a parent tracker to fix:

For both Python and Java,

Inspect all exception blocks in IOs, and ensure that they either properly handle the exception, or they rethrow the exception to be handled by the runner.

There may be rare cases where it is appropriate to not do either of the above, but those should be heavily scrutinized.

Tier 1 IOs

The Tier 1 IOs include:

  • BigQueryIO
  • BigTableIO
  • PubSubIO
  • FileIO
  • SpannerIO
  • KafkaIO
  • JdbcIO

Issue Priority

Priority: 2 (default / most normal work should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • 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
@damondouglas
Copy link
Contributor Author

.take-issue

@johnjcasey
Copy link
Contributor

@damondouglas can we close this, or is there still work to do?

@github-actions github-actions bot added this to the 2.53.0 Release milestone Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants