-
Notifications
You must be signed in to change notification settings - Fork 97
Add stubs for channel pool health checking #2634
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
base: main
Are you sure you want to change the base?
Add stubs for channel pool health checking #2634
Conversation
…ation Change-Id: I19dc8fa9d6b64f2f97b0784ec7ca8456b6b7442f
Change-Id: I92d8fece8b27d81a3c3ae996b5a1b110b7bfb495
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly: - [x] Make sure to open an issue as a [bug/issue](https://togithub.com/googleapis/java-bigtable/issues/2601) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [ ] Rollback plan is reviewed and LGTMed - [ ] All new data plane features have a completed end to end testing plan Fixes googleapis#2601 ☕️ If you write sample code, please follow the [samples format]( https://togithub.com/GoogleCloudPlatform/java-docs-samples/blob/main/SAMPLE_FORMAT.md).
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly: - [ ] Make sure to open an issue as a [bug/issue](https://togithub.com/googleapis/java-bigtable/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [ ] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) - [ ] Rollback plan is reviewed and LGTMed - [ ] All new data plane features have a completed end to end testing plan Fixes #<issue_number_goes_here> ☕️ If you write sample code, please follow the [samples format]( https://togithub.com/GoogleCloudPlatform/java-docs-samples/blob/main/SAMPLE_FORMAT.md).
Our new release job script specifies profiles that might not exist in all Java projects in our release pipeline. The requireProfileIdsExist enforcer rule fails in that case. ``` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.5.0:enforce (enforce-valid-profile) on project google-cloud-bigtable: [ERROR] Rule 0: org.apache.maven.enforcer.rules.RequireProfileIdsExist failed with message: [ERROR] The requested profile doesn't exist: release-staging-repository ``` Therefore, let's disable the requireProfileIdsExist rule during the release. This change created a profile that does that: ``` <profile> <id>enable-enforcer-rules</id> <activation> <property> <!-- By default, Maven runs the enforcer rules. The shared release script may pass profile name that doesn't exist in this project. Let's ignore the enforcer rule (requireProfileIdsExist) in that case, leveraging the presence of the performRelease property. --> <name>!performRelease</name> </property> ... ```
This should resolve the dry-run error: ``` { "pkg:maven/com.google.cloud/[email protected]": [ "Project name is missing" ], "pkg:maven/com.google.cloud/[email protected]": [ "Project name is missing" ] } ``` b/427182301
* chore(main): release 2.61.0 * chore: generate libraries at Fri Jun 27 15:32:48 UTC 2025 --------- Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: cloud-java-bot <[email protected]>
🤖 I have created a release *beep* *boop* --- ### Updating meta-information for bleeding-edge SNAPSHOT release. --- This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
…googleapis#2597) * chore: Update generation configuration at Tue Apr 29 02:30:31 UTC 2025 * chore: Update generation configuration at Wed Apr 30 02:30:32 UTC 2025 * chore: Update generation configuration at Thu May 1 02:33:38 UTC 2025 * chore: Update generation configuration at Fri May 2 02:30:49 UTC 2025 * chore: Update generation configuration at Sat Jun 7 02:32:07 UTC 2025 * chore: Update generation configuration at Tue Jun 10 02:33:39 UTC 2025 * chore: Update generation configuration at Wed Jun 11 02:32:56 UTC 2025 * chore: Update generation configuration at Thu Jun 12 02:32:34 UTC 2025 * chore: Update generation configuration at Fri Jun 13 02:32:58 UTC 2025 * chore: Update generation configuration at Sat Jun 14 02:31:48 UTC 2025 * chore: Update generation configuration at Tue Jun 17 02:33:21 UTC 2025 * chore: generate libraries at Tue Jun 17 02:33:58 UTC 2025 * chore: Update generation configuration at Wed Jun 18 02:32:47 UTC 2025 * chore: Update generation configuration at Thu Jun 19 02:33:11 UTC 2025 * chore: Update generation configuration at Fri Jun 20 02:32:53 UTC 2025 * chore: Update generation configuration at Sat Jun 21 02:32:05 UTC 2025 * chore: Update generation configuration at Wed Jun 25 02:34:28 UTC 2025 * chore: generate libraries at Wed Jun 25 02:34:58 UTC 2025 * chore: Update generation configuration at Thu Jun 26 02:33:39 UTC 2025 * chore: Update generation configuration at Fri Jun 27 02:34:16 UTC 2025 * chore: generate libraries at Fri Jun 27 19:47:33 UTC 2025 * Update clirr-ignored-differences.xml * Update BigtableTableAdminSettingsTest.java * Update BigtableTableAdminSettingsTest.java * chore: Update generation configuration at Sat Jun 28 02:32:09 UTC 2025 * chore: generate libraries at Sat Jun 28 02:32:38 UTC 2025 * chore: Update generation configuration at Sun Jun 29 02:41:31 UTC 2025 * chore: Update generation configuration at Tue Jul 1 02:42:37 UTC 2025 * fix tests * chore: Update generation configuration at Wed Jul 2 02:33:52 UTC 2025 --------- Co-authored-by: André Barbosa Sampaio <[email protected]> Co-authored-by: Mattie Fu <[email protected]>
* feat(bigtable): Add schema bundle support * minor fix * fix format * add tests * add tests * handled file * added files * fix format * fix files * fix comment * fix * fix test * fix test * fix test * fix more tests * fix more tests * fix more tests * fix more tests * fix more tests * use separate tables for tests * use separate tables for tests * use separate tables for tests * update according to PR * update according to PR * update according to PR * Update UpdateSchemaBundleRequest.java * fix build
* use mockito bom * stop using scopes in dep management Change-Id: I79ac199199b90ea8320d1a70ddef029cd3380dc1 Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly: - [ ] Make sure to open an issue as a [bug/issue](https://togithub.com/googleapis/java-bigtable/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [ ] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) - [ ] Rollback plan is reviewed and LGTMed - [ ] All new data plane features have a completed end to end testing plan Fixes #<issue_number_goes_here> ☕️ If you write sample code, please follow the [samples format]( https://togithub.com/GoogleCloudPlatform/java-docs-samples/blob/main/SAMPLE_FORMAT.md).
Change-Id: Iad08446a65b201f1ca14dfef4c8392c755f56fb4
🤖 I have created a release *beep* *boop* --- ## [2.62.0](https://togithub.com/googleapis/java-bigtable/compare/v2.61.0...v2.62.0) (2025-07-15) ### Features * Add Idempotency to Cloud Bigtable MutateRowRequest API ([b5acca6](https://togithub.com/googleapis/java-bigtable/commit/b5acca6ac4f1eec420adb27bc77aa1bda0ec2dca)) * Add SchemaBundles API ([b5acca6](https://togithub.com/googleapis/java-bigtable/commit/b5acca6ac4f1eec420adb27bc77aa1bda0ec2dca)) * **bigtable:** Add schema bundle support ([googleapis#2619](https://togithub.com/googleapis/java-bigtable/issues/2619)) ([7d7b9a9](https://togithub.com/googleapis/java-bigtable/commit/7d7b9a966d3ef7b7a0ef3f82038ab73f4d791427)) * Next release from main branch is 2.62.0 ([googleapis#2621](https://togithub.com/googleapis/java-bigtable/issues/2621)) ([202b211](https://togithub.com/googleapis/java-bigtable/commit/202b21102e71da71ff56f19a12d8a00a59cd8107)) ### Dependencies * Minor cleanup ([googleapis#2623](https://togithub.com/googleapis/java-bigtable/issues/2623)) ([7b230e8](https://togithub.com/googleapis/java-bigtable/commit/7b230e86902b5733c06e45fad90da76653ee1096)) * Update shared dependencies ([googleapis#2616](https://togithub.com/googleapis/java-bigtable/issues/2616)) ([eb7cfd5](https://togithub.com/googleapis/java-bigtable/commit/eb7cfd526aa999c614b7b8285d32759e2739ff9a)) --- This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
Change-Id: I806076a455be746f8d0ef3a63f70b53cf49f5820
Warning: This pull request is touching the following templated files:
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Change-Id: I6b2a9f7ddfcf136c295b5f9ace9943b5ee43cfa7
…datastructure of entries Change-Id: I0da4b9bad6470c0cc6b5ae168e318a1ef0620ab4
…HealthChecker Change-Id: I8068fed8c5eb49fef55ce481ef927aa33448ecae
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #2632 ☕️
If you write sample code, please follow the samples format.