openhab-addons/bundles/org.openhab.persistence.inmemory
J-N-K a1cef70277
[inmemory] Fix boundaries for queries (#16563)
Queries should include the boundaries, but the previous code did not.

Signed-off-by: Jan N. Klug <github@klug.nrw>
2024-03-24 10:31:47 +01:00
..
src [inmemory] Fix boundaries for queries (#16563) 2024-03-24 10:31:47 +01:00
NOTICE [inmemory] Initial contribution (#15063) 2023-06-24 11:15:09 +02:00
pom.xml Apply spotless after release (#16097) 2023-12-22 23:30:38 +01:00
README.md [inmemory] Initial contribution (#15063) 2023-06-24 11:15:09 +02:00

InMemory Persistence

The InMemory persistence service provides a volatile storage, i.e. it is cleared on shutdown. Because of that the restoreOnStartup strategy is not supported for this service.

The main use-case is to store data that is needed during runtime, e.g. temporary storage of forecast data that is retrieved from a binding.

Since all data is stored in memory only, there is no default strategy for this service. Unlike other persistence services, you MUST add a configuration, otherwise no data will be persisted. To avoid excessive memory usage, it is recommended to persist only a limited number of items and use a strategy that stores only data that is actually needed.

The service has a global configuration option maxEntries to limit the number of datapoints per item, the default value is 512. When the number of datapoints is reached and a new value is persisted, the oldest (by timestamp) value will be removed. A maxEntries value of 0 disables automatic purging.