[
https://issues.apache.org/jira/browse/UNOMI-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-948:
------------------------------
Description:
_PM:_ Add a missing search capability so Unomi 3 can find profiles and events
by numeric ranges (e.g. scores, ages, date windows)—needed to match planned 3.x
functionality regardless of which search backend a customer uses.
Backport the bounded property range-query API from {{unomi-3-dev}} to
{{{}master{}}}.
Scope
* Add {{rangeQuery(...)}} to {{PersistenceService}} ({{{}persistence-spi{}}})
* Implement in {{ElasticSearchPersistenceServiceImpl}} and
{{OpenSearchPersistenceServiceImpl}}
* Align {{InMemoryPersistenceServiceImpl}} test harness with the interface
(keep master review semantics)
Acceptance criteria
* Interface + ES/OS implementations compile and pass module tests
* Test harness uses {{@Override rangeQuery}} (remove duplicate test-only
helper)
* No blind checkout from {{{}unomi-3-dev{}}}; preserve master error-handling
improvements
was:
Backport the bounded property range-query API from {{unomi-3-dev}} to
{{{}master{}}}.
Scope
* Add {{rangeQuery(...)}} to {{PersistenceService}} ({{{}persistence-spi{}}})
* Implement in {{ElasticSearchPersistenceServiceImpl}} and
{{OpenSearchPersistenceServiceImpl}}
* Align {{InMemoryPersistenceServiceImpl}} test harness with the interface
(keep master review semantics)
Acceptance criteria
* Interface + ES/OS implementations compile and pass module tests
* Test harness uses {{@Override rangeQuery}} (remove duplicate test-only
helper)
* No blind checkout from {{{}unomi-3-dev{}}}; preserve master error-handling
improvements
> Add PersistenceService.rangeQuery API with Elasticsearch and OpenSearch
> implementations
> ---------------------------------------------------------------------------------------
>
> Key: UNOMI-948
> URL: https://issues.apache.org/jira/browse/UNOMI-948
> Project: Apache Unomi
> Issue Type: Sub-task
> Components: unomi(-core)
> Affects Versions: unomi-3.1.0
> Reporter: Serge Huber
> Priority: Major
> Fix For: unomi-3.1.0
>
>
> _PM:_ Add a missing search capability so Unomi 3 can find profiles and events
> by numeric ranges (e.g. scores, ages, date windows)—needed to match planned
> 3.x functionality regardless of which search backend a customer uses.
> Backport the bounded property range-query API from {{unomi-3-dev}} to
> {{{}master{}}}.
> Scope
> * Add {{rangeQuery(...)}} to {{PersistenceService}} ({{{}persistence-spi{}}})
> * Implement in {{ElasticSearchPersistenceServiceImpl}} and
> {{OpenSearchPersistenceServiceImpl}}
> * Align {{InMemoryPersistenceServiceImpl}} test harness with the interface
> (keep master review semantics)
> Acceptance criteria
> * Interface + ES/OS implementations compile and pass module tests
> * Test harness uses {{@Override rangeQuery}} (remove duplicate test-only
> helper)
> * No blind checkout from {{{}unomi-3-dev{}}}; preserve master error-handling
> improvements
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
