[BEAM-3456] Re-enable JDBC performance test#4714
Conversation
- Change number of processed records to 5 000 000 - Connect to postgres database hosted in kubernetes cluster - obtain necessary kubernetes credentials if needed - store the results in bigquery table
|
Run seed job |
|
Run Java JdbcIO Performance Test |
Remove pipeline options duplicates. The options are already defined in pkb_config_local.yaml file.
|
Run seed job |
|
Run Java JdbcIO Performance Test |
Add missing posrtgresPort (the default value is 0)
|
Run seed job |
|
Run Java JdbcIO Performance Test |
|
@chamikaramj @alanmyrvold could you take a look? I utilized the Judging from the logs the only thing that is missing right now is the bigquery table (same problem as here: https://issues.apache.org/jira/browse/BEAM-3406 ). @alanmyrvold, could we create the table? Its name is: |
|
LGTM Nice, let's get this in once we have the BQ table. |
|
Thanks, Chamikara! Actually @alanmyrvold , I'll be adding similar jenkins job for |
|
@lgajowy FYI GoogleCloudPlatform/PerfKitBenchmarker#1554 was just merged - table should now be generated automatically. |
|
Run seed job |
|
Run Java JdbcIO Performance Test |
|
Success! 😁 The table got generated thanks to the |
|
Nice. Thanks :) |
This PR re-enables the JDBC IO IT running on jenkins and kubernetes cluster. It's best to think of it as a follow up PR to #4392. back then it was impossible to run kubectl on all Jenkins executors.
The jenkins job:
Follow this checklist to help us incorporate your contribution quickly and easily:
[BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replaceBEAM-XXXwith the appropriate JIRA issue.mvn clean verifyto make sure basic checks pass. A more thorough check will be performed on your pull request automatically.