sergehuber opened a new pull request, #781: URL: https://github.com/apache/unomi/pull/781
## For project managers Unomi 3 needs a standard way to find customer profiles and events by **numeric ranges**—for example ages, scores, or date windows—when teams use either Elasticsearch or OpenSearch. This change adds that missing search capability to the product core so planned 3.x features can rely on it regardless of which search backend a deployment uses. Automated checks confirm basic range search works end-to-end; broader API test coverage is tracked separately on [UNOMI-956](https://issues.apache.org/jira/browse/UNOMI-956). ## Summary - Add `PersistenceService.rangeQuery(...)` to the persistence SPI - Implement range queries in Elasticsearch and OpenSearch persistence modules - Promote the existing in-memory test harness implementation to a proper `@Override` - Add `PersistenceServiceIT` smoke tests (numeric range + pagination) and register in `AllITs` - Strengthen unit-test `totalSize` assertions for in-memory range-query pagination ## JIRA - [UNOMI-948](https://issues.apache.org/jira/browse/UNOMI-948) — this PR - [UNOMI-956](https://issues.apache.org/jira/browse/UNOMI-956) — follow-up: full PersistenceService integration test matrix ## Test plan - [x] `mvn -pl persistence-spi install -DskipTests` then `mvn -pl services test -Dtest=InMemoryPersistenceServiceImplTest$RangeQueryTests` - [x] `mvn -pl persistence-spi,persistence-elasticsearch/core,persistence-opensearch/core -am compile` - [x] `mvn -f itests/pom.xml compile -DskipTests` - [ ] CI integration tests (`PersistenceServiceIT` via `AllITs` suite) -- 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]
