Crate re_arrow_store
source ·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
DataStore
for an overview of the core data structures. - See
DataStore::latest_at
andDataStore::range
for the documentation of the public read APIs. - See
DataStore::insert_row
for the documentation of the public write APIs.
Feature flags
-
testing
— Enables access to re_types’ test components/datatypes. -
deadlock_detection
— Enablesparking_lot
’s deadlock detection background thread. -
polars
— Integration withpolars
, to efficiently use the datastore with dataframes. -
core_benchmarks_only
— When set, only run the core set of benchmark suites. Commonly set implicitly by –all-features, e.g. on CI.
Re-exports
pub use arrow2::io::ipc::read::StreamReader;
pub use arrow2::io::ipc::read::StreamState;
pub use re_log_types::TimeInt;
pub use re_log_types::TimeRange;
pub use re_log_types::TimeType;
pub use re_log_types::Timeline;
Modules
Structs
- A complete data store: covers all timelines, all entities, everything.
- A query at a given time, for a given timeline.
- A query over a time range, for a given timeline.
- Describes an atomic change in the Rerun
DataStore
: a row has been added or deleted. - The atomic unit of change in the Rerun
DataStore
. - Incremented on each edit.
Enums
- Is it an addition or a deletion?