sergehuber opened a new pull request, #915: URL: https://github.com/apache/unomi/pull/915
## Summary - `TenantServiceImpl.getOrCreateTenant` caches the tenant after the first load/create so single-tenant compatibility mode public requests (`context.json`, event collector) no longer wait on each other or hit persistence every time (UNOMI-1002 / follow-up to UNOMI-980). - The slow path still takes a lock so concurrent first requests create the tenant exactly once. - Cache entries are dropped on `saveTenant`, `deleteTenant`, and API-key generation so updates are visible on the next call. - Compatibility mode still uses the fixed tenant id `default` only (no request header can steer it). https://issues.apache.org/jira/browse/UNOMI-1002 ## Test plan - [x] `mvn -pl services,rest test -Dtest=TenantServiceImplTest,AuthenticationFilterBlankPasswordTest` - [ ] CI unit tests - [ ] CI integration tests (Elasticsearch / OpenSearch) — existing `SingleTenantCompatibilityModeIT` (UNOMI-980) still passes -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
