feat: wire MongoDB adapter to GormRegistry O(M+N) scaling#15783
Closed
borinquenkid wants to merge 1 commit into
Closed
feat: wire MongoDB adapter to GormRegistry O(M+N) scaling#15783borinquenkid wants to merge 1 commit into
borinquenkid wants to merge 1 commit into
Conversation
This was referenced Jun 27, 2026
c9a86d8 to
112af9d
Compare
59e2f00 to
371b1c9
Compare
112af9d to
964143d
Compare
371b1c9 to
cf60629
Compare
964143d to
22a1b06
Compare
cf60629 to
6d7070a
Compare
22a1b06 to
1f3125e
Compare
6d7070a to
a597040
Compare
1f3125e to
cc888a0
Compare
a597040 to
4e0ed09
Compare
cc888a0 to
532480b
Compare
4e0ed09 to
6504e90
Compare
8294745 to
c71045d
Compare
6504e90 to
84a342e
Compare
Register MongoDB GORM APIs with GormRegistry in MongoGormEnhancer and update MongoStaticApi, affected MongoDB tests and TCK specs to use the registry-based API path. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
c71045d to
bde6eff
Compare
84a342e to
d4c2ea1
Compare
🚨 TestLens detected 38 failed tests 🚨Here is what you can do:
Test SummaryCI / Build Grails-Core (macos-latest, 21) > :grails-data-graphql-core:test
CI / Build Grails-Core (ubuntu-latest, 21) > :grails-data-graphql-core:test
CI / Build Grails-Core (ubuntu-latest, 21) > :grails-datamapping-core:test
CI / Build Grails-Core (ubuntu-latest, 25) > :grails-data-graphql-core:test
CI / Build Grails-Core Rerunning all Tasks (ubuntu-latest, 21) > :grails-data-graphql-core:test
CI / Build Grails-Core Rerunning all Tasks (ubuntu-latest, 21) > :grails-datamapping-core:test
🏷️ Commit: d4c2ea1 Test Failures (first 10 of 38)CreateEntityDataFetcherSpec > test get (:grails-data-graphql-core:test in CI / Build Grails-Core (macos-latest, 21))DeleteEntityDataFetcherSpec > test get (:grails-data-graphql-core:test in CI / Build Grails-Core (macos-latest, 21))DeleteEntityDataFetcherSpec > test get invalid (:grails-data-graphql-core:test in CI / Build Grails-Core (macos-latest, 21))EntityDataFetcherSpec (:grails-data-graphql-core:test in CI / Build Grails-Core (macos-latest, 21))SingleEntityDataFetcherSpec (:grails-data-graphql-core:test in CI / Build Grails-Core (macos-latest, 21))SoftDeleteEntityDataFetcherSpec (:grails-data-graphql-core:test in CI / Build Grails-Core (macos-latest, 21))UpdateEntityDataFetcherSpec > test get (:grails-data-graphql-core:test in CI / Build Grails-Core (macos-latest, 21))UpdateEntityDataFetcherSpec > test optimistic locking (:grails-data-graphql-core:test in CI / Build Grails-Core (macos-latest, 21))UpdateEntityDataFetcherSpec > test optimistic locking with null version (:grails-data-graphql-core:test in CI / Build Grails-Core (macos-latest, 21))CreateEntityDataFetcherSpec > test get (:grails-data-graphql-core:test in CI / Build Grails-Core (ubuntu-latest, 21))Muted Tests (first 20 of 38)Select tests to mute in this pull request:
Reuse successful test results:
Click the checkbox to trigger a rerun:
Learn more about TestLens at testlens.app. |
borinquenkid
added a commit
that referenced
this pull request
Jun 29, 2026
…ollution SchemaBasedMultiTenancySpec passed in isolation but failed in the full suite: a prior DATABASE-mode tenancy spec left a stale CompanyB->datastore binding in the singleton GormRegistry, so this SCHEMA-mode spec resolved the wrong datastore (CompanyB.DB.name 'test1Db' instead of 'test1'). Match the MongoDB adapter PR (#15783): make the datastore @shared, create it once in setupSpec after GormRegistry.reset() to clear leaked state, and keep per-feature tenant-property clearing in setup(). Applied to SchemaBasedMultiTenancySpec and MultiTenancySpec. Mongo core 3 -> 1 (only the count-OR disjunction remains). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Member
Author
|
Superseded by #15780 — the consolidated GormRegistry core-impl PR wires the in-build adapters directly (Hibernate 5/7 and MongoDB via a registered GormApiFactory; SimpleMap and GraphQL via the base GormStaticApi) and is stabilized green. The unique unit-test coverage from this stack was harvested into #15790. Closing as superseded; the branch is retained for reference (not deleted). |
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
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.
Summary
Wires the MongoDB adapter into the
GormRegistryintroduced in #15780.MongoGormApiFactory— factory that creates MongoDB-typed static, instance, and validation API instances forMongoDatastoreMongoGormInstanceApi— MongoDB-specific instance API wired through the registryMongoTransactionTemplateFactory/MongoGormTransactionTemplate/MongoTransactionContext— pluggable transaction template for MongoDB sessionsMongoStaticApi— updated to source its datastore resolver from the registryMongoGormApiFactorySpec,MongoGormInstanceApiSpec,GormRegistryScalabilitySpec,MongoTenantContextProfilingSpec,MongoGormTransactionTemplateSpec,MongoTransactionTemplateFactorySpecTest plan
./gradlew :grails-data-mongodb:testpassesStack
feat/gorm-registry-neo4j🤖 Generated with Claude Code