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

Managed BigQueryIO #31486

Open
wants to merge 19 commits into
base: master
Choose a base branch
from
Open

Conversation

ahmedabu98
Copy link
Contributor

No description provided.

@ahmedabu98
Copy link
Contributor Author

R: @chamikaramj

Copy link
Contributor

github-actions bot commented Jun 3, 2024

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

@ahmedabu98 ahmedabu98 changed the title Supported BigQueryIO as a Managed Transform Support BigQueryIO (Storage API) as a Managed Transform Jun 4, 2024
@ahmedabu98 ahmedabu98 removed this from the 2.57.0 Release milestone Jun 4, 2024
@ahmedabu98 ahmedabu98 changed the title Support BigQueryIO (Storage API) as a Managed Transform Managed BigQueryIO Jul 9, 2024
@ahmedabu98 ahmedabu98 added this to the 2.58.0 Release milestone Jul 9, 2024
@ahmedabu98
Copy link
Contributor Author

R: @chamikaramj
R: @robertwb

@ahmedabu98 ahmedabu98 removed this from the 2.58.0 Release milestone Jul 10, 2024
Copy link
Member

@kennknowles kennknowles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but this is a lot so good to get a second set of eyes. I could easily have missed something.

@@ -36,6 +36,9 @@ dependencies {
permitUnusedDeclared project(":sdks:java:io:google-cloud-platform") // BEAM-11761
implementation project(":sdks:java:extensions:schemaio-expansion-service")
permitUnusedDeclared project(":sdks:java:extensions:schemaio-expansion-service") // BEAM-11761
implementation project(":sdks:java:managed")
permitUnusedDeclared project(":sdks:java:managed") // BEAM-11761
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Notes, no action required on this PR:

  • This is a link to Jira, so probably there's a github issue it is migrated to
  • This should be equivalent to runtimeOnly because it is "implementation" but no static references to it. I would guess this works the same, or else the uberjar plugin might not treat it right.
  • Putting these deps into a docker container without making an uber jar would honestly be better in the case where it does end up in a container, so we keep the original jar metadata.

Copy link
Contributor

@chamikaramj chamikaramj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.


if (!Strings.isNullOrEmpty(configuration.getCreateDisposition())) {
CreateDisposition createDisposition =
CreateDisposition.valueOf(configuration.getCreateDisposition().toUpperCase());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a larger point, I think we should do any transform overriding in job submission (BQ modes for batch/streaming etc.) so that we can just upgrade in the backend (at least in the first version).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean making this switch in the SDK (ie. construction time)? I assumed we had settled on making it a runner side decision

Some decisions are actually dependent on the runner (e.g. at least one streaming mode in Dataflow)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean making this switch in the SDK (ie. construction time)? I assumed we had settled on making it a runner side decision

Yeah. Added some comments to the relavent doc.

@liferoad liferoad added this to the 2.60.0 Release milestone Aug 26, 2024
@ahmedabu98 ahmedabu98 removed this from the 2.60.0 Release milestone Oct 4, 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 this pull request may close these issues.

4 participants