meterstore 0.5.0

Hot/cold tiered store for metering time series — PostgreSQL for the recent window, Apache Iceberg for history.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

//! Query planning across the two tiers.
//!
//! Local calendar arithmetic is **not** here: `metering::calendar` owns the
//! `Europe/Berlin` conversion, day lengths and DST-aware interval counts. This
//! crate re-exports the parts the query layer uses so callers need not depend on
//! both, but the implementation is upstream and there is only one of it.
//!
//! # Two kinds of day
//!
//! Electricity, heat and water balance on the **Berlin calendar day**, 00:00 to
//! 00:00 local. Gas does not: the German gas market balances on the **Gastag**,
//! 06:00 to 06:00 local (GaBi Gas, following Art. 3 Nr. 6 VO (EU) 312/2014).
//! `metering` models that choice as [`DayBoundary`] and carries it through days,
//! months and years alike. The one thing this crate adds is the mapping from a
//! stored row's `sparte` to that boundary — [`day_boundary`] — because which of
//! the two applies is a fact about the row rather than about the calendar.
//! [`balancing_day`] and [`balancing_month`] are the shorthands a caller holding
//! a mixed table reaches for.

pub mod calendar;
pub mod predicate;
pub mod provider;
pub mod resolved;
pub mod split;
pub mod version;

pub use metering::calendar::{
    DayBoundary, DayKind, day_end_utc, day_kind, day_length, day_start_utc, gas_day_end_utc,
    gas_day_start_utc, intervals_in_day, local_day, local_gas_day, local_month, shift_back_days,
};

pub use calendar::{
    balancing_day, balancing_day_bounds, balancing_day_length, balancing_month, day_boundary,
    expected_intervals_in_balancing_day, gas_day_length, intervals_in_gas_day,
};
pub use predicate::{range_filters, time_range};
pub use provider::{ReadMode, SnapshotSelector, TieredTableProvider};
pub use resolved::ResolvedTableProvider;
pub use split::{TierSplit, TimeRange, split};
pub use version::{FileStats, Resolution, VersionStats, resolution_sql};