Struct MeterStoreBuilder 

pub struct MeterStoreBuilder { /* private fields */ }

Builder for MeterStore.

Implementations

impl MeterStoreBuilder

pub fn hot(self, hot: Arc<dyn HotStore>) -> Self

The hot tier.

pub fn cold( self, cold: Arc<dyn ColdStore>, provider: Arc<dyn TableProvider>, ) -> Self

The cold tier, and its DataFusion provider.

Both are needed and they are not interchangeable: the store reads the watermark through ColdStore, and scans through the provider.

pub fn table(self, config: ValidatedTableConfig) -> Self

The table configuration.

pub fn table_name(&self) -> Option<&str>

The configured table name, before the store is built.

Lets a MeterCatalog detect a duplicate before registering anything, so the error names the mistake rather than surfacing as DataFusion’s “table already exists” from inside a builder the caller did not know was being run.

pub fn registered_names(&self) -> Option<(String, String)>

The SQL names this builder will register: the raw relation, then the resolved one.

Not the same thing as the configured name, and the difference is what makes a naive uniqueness check wrong. §13.7.2 derives both from the physical name by adding or stripping _versions, so readings and readings_versions are two configurations that register exactly the same pair. register_as overrides the second, which is a third way for two tables to collide.

pub fn row_scope(self, scope: Vec<(String, ScalarValue)>) -> Self

Confine every query in this session to rows matching an identity equality.

See MeterStore::scoped, which validates the column and is the supported way to reach this.

pub fn read_mode(self, mode: ReadMode) -> Self

Restrict which tiers queries read.

pub fn session(self, ctx: SessionContext) -> Self

Build into an existing DataFusion session instead of a fresh one.

This is what lets several tables share a catalog, and therefore what makes a join across them expressible — see MeterCatalog, which is the supported way to reach it. Each table keeps its own watermark, archiver and lease (§15.3); only the query surface is shared.

pub fn subject_registry(self, registry: SubjectRegistry) -> Self

The registry backing this table’s subject column.

Required whenever the configuration declares a subject_column: without it, writes carry references that nothing can resolve and erasure has no mapping to destroy — the column would be decoration.

pub fn register_as(self, name: impl Into<String>) -> Self

Override the name the table is registered under.

pub async fn build(self) -> Result<MeterStore>

Assemble the store.

Async because the resolved table is planned from its SQL at build time.

Trait Implementations

impl Default for MeterStoreBuilder

fn default() -> MeterStoreBuilder

Returns the “default value” for a type.