-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Yaml IT - Phase 3a #34782
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
Yaml IT - Phase 3a #34782
Conversation
|
Run Python_PVR_Flink PreCommit |
|
Assigning reviewers. If you would like to opt out of this review, comment R: @claudevdm for label python. Available commands:
The PR bot will only process comments in the main thread (not review comments). |
|
Reminder, please take a look at this pr: @claudevdm @Abacn |
| Yields: | ||
| str: A JDBC connection string for the temporary MySQL database. | ||
| Example format: | ||
| "jdbc:mysql://<host>:<port>/<db_name>? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Theres quite a lot of repetition for setting up all the jdbc compatible databases. Can we simplify it by using SqlAlcemy like in jdbcio tests
| cls.engines[db_type] = sqlalchemy.create_engine( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated, thanks
|
Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment R: @damccorm for label python. Available commands:
|
|
waiting on author |
|
Run Java Precommit |
|
Seems like these failures are not related to this PR. |
damccorm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks - had one minor question, otherwise LGTM
| permitUnusedDeclared 'com.google.cloud:alloydb-jdbc-connector:1.2.0' | ||
| testImplementation library.java.junit | ||
| testImplementation library.java.mockito_core | ||
| runtimeOnly ("org.xerial:sqlite-jdbc:3.49.1.0") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be a testImplementation? Why do we need this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- My understanding is that testImplementation is for tests inside the schemaio-expansion-service module. We need the runtimeOnly so that its packaged in the jar for use later.
- It contains the driver for connecting to the DB.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, that makes sense. I think the thing we're doing here is not really a test change FWIW, it is enabling JDBCIO to connect to a new kind of DB (this is exposing a new feature in x-lang mode).
I think this is ok since we are already packaging other drivers (e.g. com.microsoft.sqlserver:mssql-jdbc:12.2.0.jre11). The only real concern I would have is the size of the jar, which seems fine.
|
Any update on this? |
|
Failures seem like flakes, so rerunning. If they pass, I will merge |
Please add a meaningful description for your change here
Phase 3 of this document - https://s.apache.org/beam-yaml-it
#34611
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.