Implement next/previous values beyond requested timespan #121
Assignees
Labels
Comments
ridoo
added a commit
to ridoo/dao-series-api
that referenced
this issue
Jul 11, 2018
Introduces the common interface `ValueAssembler` which is
implemented by both new value assemblers and older data
repositories to make step-by-step migration possible. Two
value assemblers are added at first migration step:
1. QuantityValueAssembler
2. QuantityProfileValueAssembler
Both `DatasetRespository` and `DataRespository` have been
added as proper generic Spring data repositories to make data
and dataset access work. They come with a first set of query
specifications.
Assembler instances are created at runtime depending on the
given value type (which is determined by the id, for example
`quantity_8`, or `quantity-profile_8`). This approach is not
new, but factory process has been changed slightly:
- `@ValueAssemblerComponent` is now a `@Component`
and is detected by Spring via `@ComponentScan`
- the assembler annotation takes the actual dataset type
- factory takes now that entity type to create assembler
properly according to the dataset type
Resolves: 52North#121
See also: 52North#122
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See: 52North/sensorweb-server-helgoland#440
v2.xv3.xThe text was updated successfully, but these errors were encountered: