chore(bigtable): migrate java-bigtable to monorepo #12986
Draft
chore(bigtable): migrate java-bigtable to monorepo #12986
Conversation
…#2576) This pull request is generated with proto changes between [googleapis/googleapis@2eec62d](https://togithub.com/googleapis/googleapis/commit/2eec62dc7ed836c8d9f73fb313afb8f48c361bef) (exclusive) and [googleapis/googleapis@4c2be91](https://togithub.com/googleapis/googleapis/commit/4c2be914d36599e4db46e2d77d02f3f00665cc89) (inclusive). BEGIN_COMMIT_OVERRIDE BEGIN_NESTED_COMMIT fix(deps): update the Java code generator (gapic-generator-java) to 2.59.0 END_NESTED_COMMIT BEGIN_NESTED_COMMIT chore: update the libraries_bom version to 26.61.0 END_NESTED_COMMIT END_COMMIT_OVERRIDE
🤖 I have created a release *beep* *boop* --- ## [2.60.0](https://togithub.com/googleapis/java-bigtable/compare/v2.59.0...v2.60.0) (2025-06-06) ### Features * Improve error message on malformed struct ([#2592](https://togithub.com/googleapis/java-bigtable/issues/2592)) ([b09c7cf](https://togithub.com/googleapis/java-bigtable/commit/b09c7cfbdbfb32fdf0519f16a3382b5fce729b96)) * Run ExecuteQuery conformance tests ([#2557](https://togithub.com/googleapis/java-bigtable/issues/2557)) ([6decd1a](https://togithub.com/googleapis/java-bigtable/commit/6decd1af07513366169df3abd5b64401d3800579)) ### Bug Fixes * **deps:** Update the Java code generator (gapic-generator-java) to 2.59.0 ([70f505a](https://togithub.com/googleapis/java-bigtable/commit/70f505ad504c2482dfb3668a2370b5eee57bf547)) * Ensure that multiple instances of a client in the same process dont clobber each other ([#2590](https://togithub.com/googleapis/java-bigtable/issues/2590)) ([c71b446](https://togithub.com/googleapis/java-bigtable/commit/c71b446376c3812228a980c2e6c1c26a8ef83e51)) ### Dependencies * Update shared dependencies ([#2587](https://togithub.com/googleapis/java-bigtable/issues/2587)) ([f3ae5ee](https://togithub.com/googleapis/java-bigtable/commit/f3ae5ee1de2892ea090e3d620aa9c2cbd603f3d8)) --- This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
🤖 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).
…2598) * feat: add getter for universe domain in JwtCredentialsWithAudience
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 #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/google-cloud-bigtable-emulator-core@0.198.0": [
"Project name is missing"
],
"pkg:maven/com.google.cloud/google-cloud-bigtable-deps-bom@2.61.0": [
"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 <cloud-java-bot@google.com>
🤖 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).
…#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 <andrebsamp@gmail.com> Co-authored-by: Mattie Fu <mattiefu@google.com>
* 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 ([72fa4af](https://togithub.com/googleapis/java-bigtable/commit/72fa4af94cba53dc6984b024d20be6f171ec364a)) * Add SchemaBundles API ([72fa4af](https://togithub.com/googleapis/java-bigtable/commit/72fa4af94cba53dc6984b024d20be6f171ec364a)) * **bigtable:** Add schema bundle support ([#2619](https://togithub.com/googleapis/java-bigtable/issues/2619)) ([c239111](https://togithub.com/googleapis/java-bigtable/commit/c239111964048bb96a3a82dc744e03d15162804a)) * Next release from main branch is 2.62.0 ([#2621](https://togithub.com/googleapis/java-bigtable/issues/2621)) ([1643f0e](https://togithub.com/googleapis/java-bigtable/commit/1643f0e3a4d4d667ffa0244b090e6ad1738182a9)) ### Dependencies * Minor cleanup ([#2623](https://togithub.com/googleapis/java-bigtable/issues/2623)) ([b334032](https://togithub.com/googleapis/java-bigtable/commit/b334032e3dbad58c7b077762df86770d3fc9ea55)) * Update shared dependencies ([#2616](https://togithub.com/googleapis/java-bigtable/issues/2616)) ([ff5abf9](https://togithub.com/googleapis/java-bigtable/commit/ff5abf9c5827e73c824ae8b4cf214b71c3788ec3)) --- 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
Change-Id: I10bfd50174fe2c790aa4a10086a3b14017ba6156 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).
🤖 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).
Change-Id: I273e614ab8d5e8e1bf73e031e80729dda0b2f0de
Change-Id: I56119f9cce8abe8317fc9580a13f4588035de80d
#2620) This pull request is generated with proto changes between [googleapis/googleapis@63161c0](https://togithub.com/googleapis/googleapis/commit/63161c080e7eb3dd1d4fe76db1fad108b6ac9a27) (exclusive) and [googleapis/googleapis@0da61b4](https://togithub.com/googleapis/googleapis/commit/0da61b4af3b87dd71dd557457b5099e23154b297) (inclusive). BEGIN_COMMIT_OVERRIDE BEGIN_NESTED_COMMIT feat: add Idempotency to Cloud Bigtable MutateRowsRequest API docs: Minor comment update for field `idempotency` in message `.google.bigtable.v2.MutateRowRequest` PiperOrigin-RevId: 785585326 Source Link: [googleapis/googleapis@0da61b4](https://togithub.com/googleapis/googleapis/commit/0da61b4af3b87dd71dd557457b5099e23154b297) END_NESTED_COMMIT BEGIN_NESTED_COMMIT docs: Sync generated comments from the API Protos PiperOrigin-RevId: 785555034 Source Link: [googleapis/googleapis@5feffd9](https://togithub.com/googleapis/googleapis/commit/5feffd940877775c76330c4e37cc139979fccd72) END_NESTED_COMMIT BEGIN_NESTED_COMMIT feat: add type support for Proto and Enum PiperOrigin-RevId: 783889912 Source Link: [googleapis/googleapis@ff47072](https://togithub.com/googleapis/googleapis/commit/ff470725e0d32afab5d827767ff2df73fa1ad37c) END_NESTED_COMMIT END_COMMIT_OVERRIDE
* chore: create LTS branch 2.60.x * fix: match unittests run for main branch
#2640) * chore: Update generation configuration at Wed Jul 23 02:40:33 UTC 2025 * chore: Update generation configuration at Thu Jul 24 02:40:02 UTC 2025 * chore: generate libraries at Thu Jul 24 02:40:33 UTC 2025
meltsufin
force-pushed
the
migrate-java-bigtable
branch
11 times, most recently
from
4d355be to
ea7486d
Compare
…ter changes matrix
meltsufin
force-pushed
the
migrate-java-bigtable
branch
from
93fa97e to
ff1c7a2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Using script from here: #12962.