Expand description
The Rerun datastore, implemented on top of Apache Arrow
using the arrow2 crate.
This crate is an in-memory time series database for Rerun log data.
It is indexed by entity path, component, timeline, and time.
It supports out-of-order insertions, and fast O(log(N)) queries.
- See
DataStorefor an overview of the core data structures. - See
DataStore::latest_atandDataStore::rangefor the documentation of the public read APIs. - See
DataStore::insert_rowfor the documentation of the public write APIs.
§Feature flags
deadlock_detection— Enablesparking_lot’s deadlock detection background thread.
Re-exports§
pub use arrow2::io::ipc::read::StreamReader;pub use arrow2::io::ipc::read::StreamState;pub use re_log_types::ResolvedTimeRange;pub use re_log_types::TimeInt;pub use re_log_types::TimeType;pub use re_log_types::Timeline;
Modules§
Structs§
- Data
Store - A complete data store: covers all timelines, all entities, everything.
- Data
Store Config - Data
Store RowStats - Data
Store Stats - Entity
Stats - Garbage
Collection Options - Latest
AtQuery - A query at a given time, for a given timeline.
- Range
Query - A query over a time range, for a given timeline.
- Store
Diff - Describes an atomic change in the Rerun
DataStore: a row has been added or deleted. - Store
Event - The atomic unit of change in the Rerun
DataStore. - Store
Generation - Incremented on each edit.
- Store
Subscriber Handle
Enums§
- Garbage
Collection Target - Store
Diff Kind - Is it an addition or a deletion?
- Write
Error
Traits§
- Store
Subscriber - A
StoreSubscribersubscribes to atomic changes from allDataStores throughStoreEvents.